International Edition (VPAT® Version 2.5 INT)
Name of Product/Version: Simple Reports Apps Suite — Release of 14 September 2026
Report Date: 14 September 2026
Vendor:
Agilis LT, MB is a software development company specializing in analytical and reporting apps for Atlassian Jira, headquartered in Vilnius, Lithuania. Its goal is to develop apps that are simple to use yet powerful enough to provide actionable insights that help businesses make better decisions.
Product Description:
Simple Reports Apps Suite provides enhanced reporting and data visualization capabilities for teams using Atlassian Jira. These apps integrate into Jira to offer custom reports and interactive dashboards that go beyond Jira's built-in reporting features. The suite and the apps it includes are listed on the Atlassian Marketplace at https://marketplace.atlassian.com/vendors/1215481.
Key features are custom report generation, with filters, groupings and sorting beyond Jira's default reporting tools; interactive dashboards and gadgets that embed real-time data visualizations directly into Jira dashboards; and a secure-by-design architecture in which data is processed in real time and is not stored externally, so that all data remains within the host product.
The apps are delivered as Atlassian Forge applications that render within an iframe in the Jira interface. Typical users are project managers tracking sprint progress and burndown trends, agile teams generating velocity charts, and executives and stakeholders reviewing project health through custom dashboards.
The suite comprises ten applications:
|
Application, as listed on the Atlassian Marketplace |
Interfaces |
|---|---|
|
Simple Custom Reports, Charts & Dashboard Gadgets for Jira |
Reporting application, report menu, global settings, dashboard gadgets |
|
Simple Reports Lite – Free Reports & Charts for Jira |
Reduced edition of the above |
|
Advanced Burndown Chart Dashboard Gadget for Jira |
Gadget view and configuration panel |
|
Individual Velocity Chart/Report Dashboard Gadget for Jira |
Gadget view and configuration panel |
|
Simple Timesheet & Worklog Dashboard Gadget for Jira |
Gadget view and configuration panel |
|
Time Tracking & Estimation Report Dashboard Gadget for Jira |
Gadget view and configuration panel |
|
Status & Progress Report, Sum Up Dashboard Gadget for Jira |
Gadget view and configuration panel |
|
Time in Status Report Dashboard Gadget for Jira |
Gadget view and configuration panel |
|
Simple Gantt & Roadmap Timeline Dashboard Gadget for Jira |
Gadget view and configuration panel |
|
Free JQL Filter Counter & KPI Dashboard Gadget for Jira |
Gadget view and configuration panel |
Seven of these applications are additionally deployed to Atlassian Government Cloud. Those deployments are within the scope of this report. They are built from the same source and publish the identical application bundle as the commercial cloud listings, so the user interface, and therefore every conformance statement below, is the same in both environments. The environments differ only in ways that do not affect the user interface.
Each gadget presents two interfaces: a view that renders reports, tables and charts, and a configuration panel of form controls. Every interface listed above was included in this evaluation.
Contact Information: info@simple-reports.com
Notes:
This is a self-evaluation performed by Agilis LT, MB. No independent third-party accessibility audit has been conducted. Any other attestation the vendor holds covers different subject matter and does not extend to the contents of this report.
Where a criterion is marked Supports, the basis is stated in the Remarks column. Criteria resting on automated testing alone are identified as such, because automated tools cover only part of any success criterion.
Evaluation Methods Used:
Testing was performed against the applications running with representative data, in Google Chrome (Chromium) on Windows, in both light and dark themes.
-
Automated scanning. axe-core, driven by Playwright, across 56 application views — 24 gadget views, 12 gadget configuration panels, 7 views of the Simple Reports application, the global settings page, and 12 dark-theme variants of the views that carry colour. Rules applied: WCAG 2.0 A/AA and WCAG 2.1 A/AA. Result: zero violations. Each view asserts it rendered content before being scanned, so a scan of an empty page cannot be recorded as a pass.
-
Keyboard testing. A scripted walk of 44 views using real Tab key presses, recording at every stop the focused element, the accessible name an assistive technology would resolve, whether a visible focus indicator is painted, and whether focus ultimately reaches the browser chrome. Result: 737 focus stops, no keyboard traps, and no stop without a visible focus indicator. A screenshot was captured at each stop.
-
Manual inspection. Review of the recorded focus order against the visual layout; review of every chart's text alternative against its live rendered output; measurement of every foreground/background colour pair that automated scanning flagged, and of the pairs it cannot sample reliably; reflow testing at 320 CSS pixels; text resize testing at 200%; and text spacing testing against the overrides required by success criterion 1.4.12.
Limitations of this evaluation — these are stated so that a reader can weigh the results:
-
Automated keyboard testing counts only elements a browser treats as focusable. An element that handles clicks but carries no
tabindexis invisible to it, and is reported neither as a control nor as a control that was missed. Because automation cannot see this pattern, every click handler in the product source was additionally reviewed by hand. That review found more instances than automation had reported; the navigation controls among them were corrected and the remainder are recorded as exceptions under 2.1.1. The focus stop count above therefore measures what is reachable, not what ought to be. -
Two chart components and one chart mode were not rendered during testing. The bar chart and doughnut chart in the Simple Reports application, and the velocity chart in one of its display modes, are not reachable with the test data available. Their text alternatives were verified by code inspection and are structurally identical to charts that were verified at runtime.
-
Colour testing in the light theme resolves design-token fallback values. Where a colour is expressed as a design token with a fallback, the test environment renders the fallback while production resolves the token. Every such token used by the product was therefore checked against both values. Of the five that carry a colour, four meet their requirement in both environments; only the input boundary differs materially, and it falls short in production as well as in test — recorded under 1.4.11. No result in this report depends on the test environment's fallback values.
-
Four of the heatmap gadget's five colour schemes were measured but not rendered during testing, as no test configuration uses them.
-
Testing was performed in one browser engine. Assistive-technology testing with screen reader software was not performed.
Applicable Standards/Guidelines:
|
Standard/Guideline |
Included In Report |
|---|---|
|
Web Content Accessibility Guidelines 2.1 |
Level A — Yes; Level AA — Yes; Level AAA — No |
|
Revised Section 508 standards (published January 2017) |
Yes |
|
EN 301 549 Accessibility requirements for ICT products and services — V3.2.1 (2021-03) |
Yes |
Terms:
-
Supports — the functionality of the product has at least one method that meets the criterion without known defects, or meets the criterion with equivalent facilitation.
-
Partially Supports — some functionality of the product does not meet the criterion.
-
Does Not Support — the majority of product functionality does not meet the criterion.
-
Not Applicable — the criterion is not relevant to the product.
-
Not Evaluated — the product has not been evaluated against the criterion.
WCAG 2.1 Report
Tables 1 and 2 document conformance with WCAG 2.1. Level AAA was not evaluated.
Table 1: Success Criteria, Level A
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
1.1.1 Non-text Content |
Partially Supports |
All five chart components expose a text alternative on the chart canvas summarising the measure, the number of series and categories, and their names — verified against live output. Informational images in the documentation view carry alt text. Exception: the burndown gadget presents a chart with no equivalent table, so its text alternative is a summary rather than an equivalent of the plotted data. The Simple Reports application and the velocity gadget present the same data as tables alongside their charts. |
|
1.2.1 Audio-only and Video-only (Prerecorded) |
Not Applicable |
The product contains no audio or video content. |
|
1.2.2 Captions (Prerecorded) |
Not Applicable |
The product contains no audio or video content. |
|
1.2.3 Audio Description or Media Alternative (Prerecorded) |
Not Applicable |
The product contains no audio or video content. |
|
1.3.1 Info and Relationships |
Partially Supports |
The principal data tables use header cells, and the heatmap gadget is a fully headed two-axis grid whose column and row headers, including its totals, carry explicit |
|
1.3.2 Meaningful Sequence |
Supports |
Focus order was recorded across 44 views and follows DOM order, which matches the visual reading order in every view reviewed. |
|
1.3.3 Sensory Characteristics |
Supports |
Instructions do not rely on shape, size, or visual location alone. Where chart options refer to line styling, the option is also named in text (for example "Ideal burn (dashed line)"). |
|
1.4.1 Use of Colour |
Partially Supports |
Links that appear inside running text are underlined throughout, so colour is not the only indicator; this was reviewed site by site across 35 declaration sites plus the generated work-item key lists. Standalone links retain the platform's colour-only styling, which this criterion does not reach. Exception: chart series are distinguished by colour. The burndown chart additionally separates its ideal and actual lines by line style, but its per-assignee series are distinguished by colour alone, and it is the only chart view without an accompanying table. |
|
1.4.2 Audio Control |
Not Applicable |
The product contains no audio. |
|
2.1.1 Keyboard |
Partially Supports |
All 737 recorded focus stops across 44 views are reachable by keyboard, and all form controls, buttons and links are operable. Navigation is fully keyboard operable: the report-selection menu, the application tab bar, the board and epic selectors, and the collapsible sections of the global settings page all take focus, carry a role, and are activated by Enter or Space. Exceptions: certain controls within reports and gadget configuration are rendered as elements that respond only to pointer events — sorting a table column, expanding a grouped row, opening the status-history panel, and the Import/Export configuration items in gadget settings. The data itself remains readable, and no functionality requires timed or path-dependent keystrokes. |
|
2.1.2 No Keyboard Trap |
Supports |
In all 44 views tested, focus advances out of the application to the browser chrome; no trap was found. |
|
2.1.4 Character Key Shortcuts |
Not Applicable |
The product implements no single-character key shortcuts. |
|
2.2.1 Timing Adjustable |
Not Applicable |
The product imposes no time limits on user activity. |
|
2.2.2 Pause, Stop, Hide |
Partially Supports |
No content moves, blinks or scrolls. Exception: the countdown gadget displays a continuously updating remaining-time value with no pause, stop or hide control. The updating value is the purpose of that gadget; the same information is present as a target date, which does not update. |
|
2.3.1 Three Flashes or Below Threshold |
Supports |
No content flashes. |
|
2.4.1 Bypass Blocks |
Supports |
Gadget views contain no repeated blocks of content. In the Simple Reports application the report menu occupies a single focus stop, so no bypass mechanism is required to reach the main content. |
|
2.4.2 Page Titled |
Supports |
Each application document carries a descriptive title. Confirmed by automated testing across 56 views. |
|
2.4.3 Focus Order |
Supports |
Focus order was recorded per view and reviewed against the visual layout. In the configuration panels it follows the form top to bottom, ending on the save and cancel actions; in data views it follows the reading order of the content. |
|
2.4.4 Link Purpose (In Context) |
Supports |
Link purpose is determinable from the link text together with its sentence or table context. Work-item links additionally carry a descriptive title. Confirmed by automated testing across 56 views. |
|
2.5.1 Pointer Gestures |
Supports |
All pointer operations are single-point activations; no path-based or multipoint gestures are used. |
|
2.5.2 Pointer Cancellation |
Supports |
Activation occurs on the up-event through standard platform event handling. |
|
2.5.3 Label in Name |
Supports |
Where a control receives a programmatic label, that label repeats the text of its visible label. |
|
2.5.4 Motion Actuation |
Not Applicable |
No functionality is operated by device or user motion. |
|
3.1.1 Language of Page |
Supports |
The document declares |
|
3.2.1 On Focus |
Supports |
Receiving focus does not initiate a change of context. |
|
3.2.2 On Input |
Supports |
Changing a filter or setting updates the displayed report but does not change context — focus is not moved, and no new window is opened. |
|
3.3.1 Error Identification |
Partially Supports |
Input errors in configuration panels are identified visually on the field concerned. Exception: error identification was not tested systematically across every form, and errors are not announced programmatically — see 4.1.3. |
|
3.3.2 Labels or Instructions |
Supports |
Every form control carries a programmatic label, including controls provided by third-party components whose visible labels are not natively associated. Confirmed by automated testing across the 12 configuration panels and the global settings page. |
|
3.3.3 Error Suggestion |
Partially Supports |
Where input format is constrained, the expected format is described in adjacent help text with a link to its specification. Correction suggestions are not offered programmatically for all fields. |
|
3.3.4 Error Prevention (Legal, Financial, Data) |
Not Applicable |
The product does not carry out legal or financial transactions and does not modify or delete user-controllable data; it reads and reports on data held in Jira. Configuration changes are reversible from the same panel. |
|
4.1.1 Parsing |
Supports |
Confirmed by automated testing across 56 views. |
|
4.1.2 Name, Role, Value |
Supports |
All user interface components expose a name and role, and state is exposed programmatically. Confirmed by automated testing across 56 views in both themes, including all configuration panels. |
Table 2: Success Criteria, Level AA
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
1.2.4 Captions (Live) |
Not Applicable |
The product contains no live media. |
|
1.2.5 Audio Description (Prerecorded) |
Not Applicable |
The product contains no video content. |
|
1.3.4 Orientation |
Supports |
Display is not restricted to a single orientation. |
|
1.3.5 Identify Input Purpose |
Not Applicable |
The product collects no information about the user; its input fields configure reports. |
|
1.4.3 Contrast (Minimum) |
Supports |
Every foreground/background pair identified during testing was measured and meets or exceeds 4.5:1 in both themes. Corrections were made to the heatmap gadget's cell palettes (lowest measured pair before correction 1.77:1, now 7.96:1) and to the Gantt gadget's bar labels, progress fills and current-period column, in both light and dark themes. Values are hard-coded or derived from application-defined variables, so measured values are those rendered in production. See the evaluation limitations regarding heatmap colour schemes not rendered during testing. |
|
1.4.4 Resize text |
Supports |
Content and functionality remain available at 200% text size; no content was lost in the views tested. |
|
1.4.5 Images of Text |
Supports |
Text is rendered as text. Images are used only for illustrative screenshots in the documentation view. |
|
1.4.10 Reflow |
Supports |
At 320 CSS pixels the views tested reflow without horizontal scrolling of the page. Wide data grids scroll horizontally within their own container, which the criterion permits for data tables. |
|
1.4.11 Non-text Contrast |
Partially Supports |
The keyboard focus indicator meets the 3:1 requirement against its background in both themes. Select and input boundaries were measured: in the dark theme they meet the requirement (4.5:1 and above), and in the light theme they meet it against a white background (3.2:1). Exception: in the light theme the same boundary measures 2.97:1 against the shaded surface used by configuration panels, marginally below the 3:1 requirement. Exception — chart series colours: series are drawn at 75% opacity, and over the white plot area four of the seven base colours measure below 3:1 (yellow 1.63:1, teal 1.95:1, green 2.07:1, red 2.46:1); the remaining three pass (purple 3.46:1, blue 4.07:1, navy 6.36:1). Charts carry a text alternative, and in every chart view except the burndown gadget the same data is presented as a table. Not measured: the boundaries of every component supplied by third-party libraries. |
|
1.4.12 Text Spacing |
Supports |
With line height set to 1.5 times the font size, letter spacing to 0.12em, word spacing to 0.16em and paragraph spacing to 2em, no content was lost and no text was clipped by its container. Verified across a sample of five views covering a configuration panel, a summary view, a timesheet table, a data grid and a metric card layout. |
|
1.4.13 Content on Hover or Focus |
Partially Supports |
Tooltips provide additional detail on hover and on keyboard focus. Dismissible is met: the tooltip is closed by the Escape key without moving pointer or focus. Persistent is met: the tooltip remains visible while the trigger holds focus. Exception — Hoverable is not met: the tooltip is dismissed when the pointer is moved onto the tooltip itself, so its text cannot be reached with the pointer. Tooltip text duplicates information available elsewhere in the interface or repeats a control's accessible name. |
|
2.4.5 Multiple Ways |
Not Applicable |
Each application is a single view or a single application with one navigation mechanism; it is not a set of web pages. |
|
2.4.6 Headings and Labels |
Supports |
Headings and labels describe their topic or purpose. Confirmed by automated testing across 56 views. |
|
2.4.7 Focus Visible |
Supports |
Every one of the 737 recorded focus stops paints a visible focus indicator. This includes controls whose real input is visually hidden by a third-party component and drawn as a separate element, where the indicator is applied to the element the user can see. |
|
3.1.2 Language of Parts |
Not Applicable |
All content is presented in a single language. |
|
3.2.3 Consistent Navigation |
Supports |
Navigation mechanisms are presented in the same relative order throughout. |
|
3.2.4 Consistent Identification |
Supports |
Components with the same functionality are identified consistently across the suite, which shares one component library. |
|
3.3.3 Error Suggestion |
Partially Supports |
See 3.3.3 in Table 1. |
|
4.1.3 Status Messages |
Does Not Support |
Status changes — loading progress, the empty-result message, and the result of applying a filter — are presented visually but are not exposed through a live region or status role, so they are not announced by assistive technology without a change of focus. |
Revised Section 508 Report
Chapter 3: Functional Performance Criteria (FPC)
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
302.1 Without Vision |
Partially Supports |
All controls, tables and form fields expose names, roles and values, and navigation is operable by keyboard. Charts expose a summarising text alternative. Exceptions: some controls within reports and gadget configuration cannot be operated without a pointing device (see 2.1.1); status messages are not announced (see 4.1.3); the burndown chart's data is available only as a summary, not as an equivalent table. |
|
302.2 With Limited Vision |
Supports |
Text meets 4.5:1 contrast, content reflows at 320 CSS pixels, and content remains available at 200% text size. |
|
302.3 Without Perception of Colour |
Partially Supports |
Links in running text are underlined. Exception: chart series are distinguished by colour; see 1.4.1. |
|
302.4 Without Hearing |
Not Applicable |
The product conveys no information through sound. |
|
302.5 With Limited Hearing |
Not Applicable |
The product conveys no information through sound. |
|
302.6 Without Speech |
Not Applicable |
The product requires no speech input. |
|
302.7 With Limited Manipulation |
Partially Supports |
Navigation is operable by keyboard; the exceptions at 2.1.1 apply. No path-based or multipoint gestures are required. |
|
302.8 With Limited Reach and Strength |
Supports |
No operation requires simultaneous actions, sustained input, or fine motor control beyond single-point activation. |
|
302.9 With Limited Language, Cognitive, and Learning Abilities |
Supports |
The product provides help text adjacent to configuration fields, consistent navigation and consistent identification of components. |
Chapter 4: Hardware
Not Applicable — the product is software delivered as a web application and includes no hardware.
Chapter 5: Software
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
501.1 Scope |
— |
The product is software with a user interface; see the WCAG 2.1 report above, which applies in full. |
|
502.2.1 User Control of Accessibility Features |
Not Applicable |
The product is a web application within a host browser and does not alter platform accessibility features. |
|
502.2.2 No Disruption of Accessibility Features |
Supports |
The product does not disrupt platform accessibility features. |
|
502.3 Accessibility Services |
Partially Supports |
The product exposes object information, state, name and role through standard web platform accessibility APIs, including expanded state on the global settings disclosures and the current selection in the report menu and application tab bar. See exceptions at 2.1.1 and 4.1.3. |
|
502.4 Platform Accessibility Features |
Not Applicable |
The product is not a platform. |
|
503.2 User Preferences |
Supports |
The product honours the host platform's colour theme, and text scales with browser and platform text size settings. |
|
503.3 Alternative User Interfaces |
Not Applicable |
The product provides no alternative user interface. |
|
503.4 User Controls for Captions and Audio Description |
Not Applicable |
The product contains no media. |
|
504 Authoring Tools |
Not Applicable |
The product is not an authoring tool. It generates reports from data held in Jira and does not produce content for publication by the user. |
Chapter 6: Support Documentation and Services
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
601.1 Scope |
— |
See below. |
|
602.2 Accessibility and Compatibility Features |
Partially Supports |
Product documentation is published as web content at the vendor's documentation site. This report is the record of accessibility and compatibility features; the documentation itself does not yet describe them. |
|
602.3 Electronic Support Documentation |
Not Evaluated |
The vendor's documentation site was not within the scope of this evaluation. |
|
602.4 Alternate Formats for Non-Electronic Support Documentation |
Not Applicable |
No non-electronic documentation is provided. |
|
603.2 Information on Accessibility and Compatibility Features |
Supports |
Accessibility enquiries are accepted at info@simple-reports.com. |
|
603.3 Accommodation of Communication Needs |
Supports |
Support is provided by email, which accommodates a range of communication needs. |
EN 301 549 Report
Chapter 4: Functional Performance
See Chapter 3 of the Section 508 report above; clauses 4.2.1 to 4.2.11 correspond to criteria 302.1 to 302.9 with the addition of the clauses below.
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
4.2.10 Privacy |
Supports |
The product provides no accessibility feature that reduces the privacy afforded to other users. |
|
4.2.11 Approach to Functional Performance |
Supports |
See Chapter 3 above. |
Chapter 5: Generic Requirements
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
5.1 Closed Functionality |
Not Applicable |
The product does not have closed functionality; assistive technology can be attached through the host browser. |
|
5.2 Activation of Accessibility Features |
Supports |
Accessibility features are always active; no activation step is required. |
|
5.3 Biometrics |
Not Applicable |
The product uses no biometrics. |
|
5.4 Preservation of Accessibility Information During Conversion |
Not Applicable |
The product performs no conversion of content. |
|
5.5 Operable Parts |
Partially Supports |
Operable parts are discernible and operable without grasping or twisting. See the keyboard exceptions at 2.1.1. |
|
5.6 Locking or Toggle Controls |
Supports |
Toggle state is exposed programmatically and visually. |
|
5.7 Key Repeat |
Not Applicable |
Key repeat is controlled by the host platform. |
|
5.8 Double-Strike Key Acceptance |
Not Applicable |
Controlled by the host platform. |
|
5.9 Simultaneous User Actions |
Supports |
No operation requires simultaneous user actions. |
Chapter 6: ICT with Two-Way Voice Communication
Not Applicable — the product provides no two-way voice communication.
Chapter 7: ICT with Video Capabilities
Not Applicable — the product provides no video capabilities.
Chapter 8: Hardware
Not Applicable — the product includes no hardware.
Chapter 9: Web
The product's web content conforms as recorded in the WCAG 2.1 report above. Clauses 9.1 through 9.4 correspond to WCAG 2.1 Level A and AA success criteria; see Tables 1 and 2.
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
9.1 – 9.4 (WCAG 2.1 A and AA) |
Partially Supports |
See Tables 1 and 2. The exceptions are 1.1.1, 1.3.1, 1.4.1, 1.4.11, 1.4.13, 2.1.1, 2.2.2, 3.3.1, 3.3.3 and 4.1.3. |
|
9.5 Non-Interference |
Supports |
No content flashes, plays audio automatically, or traps keyboard focus. |
Chapter 10: Non-web Documents
Not Applicable — the product produces no non-web documents. Report output is printed through the browser's own print function, which renders the web content already covered above.
Chapter 11: Software
Clauses 11.1 to 11.6 correspond to the WCAG 2.1 criteria recorded in Tables 1 and 2, applied to the product's user interface.
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
11.1 – 11.6 (WCAG 2.1 A and AA) |
Partially Supports |
See Tables 1 and 2. |
|
11.7 User Preferences |
Supports |
The product follows the host platform's colour theme and text size settings. |
|
11.8 Authoring Tools |
Not Applicable |
The product is not an authoring tool. |
Chapter 12: Documentation and Support Services
|
Criteria |
Conformance Level |
Remarks and Explanations |
|---|---|---|
|
12.1.1 Accessibility and Compatibility Features |
Partially Supports |
See 602.2 above. |
|
12.1.2 Accessible Documentation |
Not Evaluated |
The vendor's documentation site was not within the scope of this evaluation. |
|
12.2.2 Information on Accessibility and Compatibility Features |
Supports |
See 603.2 above. |
|
12.2.3 Effective Communication |
Supports |
See 603.3 above. |
|
12.2.4 Accessible Documentation |
Not Evaluated |
See 12.1.2. |
Chapter 13: ICT Providing Relay or Emergency Service Access
Not Applicable — the product provides no relay or emergency service access, and no functionality relating to hearing aid compatibility or caption/audio-description delivery.
Known Issues and Planned Remediation
The exceptions recorded above are summarised here for planning purposes.
|
Issue |
Criteria |
Status |
|---|---|---|
|
Table sorting, grouped-row expansion, the status-history panel and gadget Import/Export are not keyboard operable |
2.1.1, 302.1, 302.7, 5.5 |
Known. Navigation was remediated; these remain. A remediation approach has been identified. |
|
Status messages are not announced to assistive technology |
4.1.3, 302.1 |
Known. No live regions are currently implemented. |
|
Chart series are distinguished by colour |
1.4.1, 302.3 |
Known. Data is available as tables in all chart views except the burndown gadget. |
|
Burndown gadget provides no tabular equivalent of its chart |
1.1.1, 302.1 |
Known. |
|
Two gadgets use table markup for a non-tabular layout; heatmap grid has no caption |
1.3.1 |
Known. Heatmap headers are fully associated. |
|
Countdown gadget auto-updates without a pause control |
2.2.2 |
Known. |
|
Input boundaries measure 2.97:1 on the configuration panel surface in the light theme |
1.4.11 |
Known; 0.03 below the requirement. Dark theme and white backgrounds pass. |
|
Four of seven chart series colours fall below 3:1 against the plot area |
1.4.11 |
Known. Series are drawn at 75% opacity; lowest measured 1.63:1. |
|
Tooltip content cannot be hovered; it dismisses when the pointer moves onto it |
1.4.13 |
Known. Dismissible and persistent requirements are met. |
|
Documentation site not evaluated |
602.3, 12.1.2, 12.2.4 |
Out of scope of this evaluation. |
"VPAT" is a registered service mark of the Information Technology Industry Council (ITI).