...
Review of product vs A and AA standards (AAA standard is somethign we may look at in future).
Lots of items need further checking / analysis. Items where we know we fall short marked in red, items where we know we comply marked in green.
Level A
Principle | Status | Comments |
|---|---|---|
1.1 Test Alternatives | Several issues - see Accessibility Testing with Google Accessibility Scanner | SAF-683 |
1.2 Time Based Media | N/A | No examples of Time Based Media |
1.3Adaptable1.3.1 Info and RelationshipsInformation, structure, and relationships conveyed through presentation can be programmatically determined or are available in text. | Unclear - Exposure Notifications Page needs review | |
1.3.2 Meaningful Sequence | N/A | Don’t believe there is any content where this applies. |
1.3.3 Sensory CharacteristicsInstructions provided for understanding and operating content do not rely solely on sensory characteristics of components such as shape, color, size, visual location, orientation, or sound. | Needs review | We use colour a lot for status indications. I suspect we don’t solely use clour so probable OK but needs some review. |
1.4.1 Use of ColorColor is not used as the only visual means of conveying information, indicating an action, prompting a response, or distinguishing a visual element. | Needs review | See 1.3.3 above |
1.4.2 Audio Control | N/A | We don’t have any audio content to which this might apply. |
2.1 Keyboard Accessible2.1.1, 2.1.2 and 2.1.4 apply at level A | Needs review | Believe this would not be applicable for a Web App, but we should confirm. |
2.2 Enough Time2.2.1 and 2.2.2 apply at level A | Needs review | Not aware of any time-limited content in the App, but we should check carefully. |
2.3 Seizures and Physical Reactions | Compliant | We have no content that flashes more than 3 times / second. |
2.4.1 Bypass Blocks | Needs review | We should review for repeated content, and remove or add a bypass if needed. |
2.4.2 Page Titled | Needs review | Check all pages have suitable titles |
2.4.3 Focus Order | Applicable? | Believe this does not apply for a mobile app - need to review that. |
2.4.4 Link Purpose (In Context) | Needs review | Review all links for clarity of purpose (in context) |
2.5.1 Pointer Gestures | Needs review (though I believe we don’t use multi-point or path-based gestures anyway). | Does this apply to be continued…Mobile apps? |
2.5.3 Label in Name | Needs review | Does the name always match the text that is visually presented? |
2.5.4 Motion Actuation | N/A | We don’t have any functions activated by device or user motion. (Location movement is assumed not to count). |
3.1.1 Language of Page | Needs checking | Can language of every page be programmatically determined? |
3.2.1 On Focus | N/A | I don’t believe the concept of “Focus” applies in our app. |
3.2.2 On Input | Compliant | No location where input of data causes a change of context |
3.3.2 Labels or Instructions | Needs checking | Check that all user inputs provide labels or instructions. |
4.1.1 Parsing | Needs checking: “In content implemented using markup languages, elements have complete start and end tags, elements are nested according to their specifications, elements do not contain duplicate attributes, and any IDs are unique, except where the specifications allow these features.” | Some non-unique IDs identified by Google Accessibility Scanner - need attention. SAF-684 |
4.1.2 Name, Role, Value | Needs checking: “For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined;” | According to notes likely we meet this already assuming we have not rolled our own UI components anywhere. |
AA standard
Principle | Status | Comments |
|---|---|---|
1.2 Time Based Media | N/A | No examples of Time Based Media |
1.3.4 Orientation | Would need to work in Landscape mode | Not something we support today. |
1.3.5 Identify Input Purpose | Needs review | “The purpose of each input field collecting information about the user can be programmatically determined” |
1.4.3 Contrast (Minimum) | Current (4/6) code falls short but UI redesign may addeess this | |
1.4.4 Resize text | Not supported today | |
1.4.5 Images of Text | To check | To check whether we use images of text anywhere in the app |
1.4.10 Reflow | Relates to resizing of text | Not supported today |
1.4.11 Non-text Contrast | To check | Lower contrast ratio (3:1 not 4.5:1 so we may be OK here) |
1.4.12 Text Spacing | To check whether we meet all the standards here. | |
1.4.13 Content on Hover or Focus | Not sure if this applies | Does “hover” have meaning on a mobile app? |
2.4.5 Multiple Ways | Current design does not meet this. | Requirement is for Multiple Ways to access each page (except those in a process flow) |
2.4.6 Headings and Labels | To check | “Headings and labels describe topic or purpose.” |
2.4.7 Focus Visible | N/A? - to check | I don’t believe this is meaningful for a Mobile App. |
3.1.2 Language of Parts | Needs checking | Can “The human language of each passage or phrase in the content can be programmatically determined “ |
3.2.3 Consistent Navigation | Not compliant today | See e.g. SAF-209. May get better after 5/6 UI rework? |
3.2.4 Consistent Identification | Needs checking across the app | Same elements on different pages should have same identifiers. |
3.3.3 Error Suggestion | Needs checking for all text inputs. | Only text input is “HA by URL, and we’re removing that?” |
3.3.4 Error Prevention (Legal, Financial, Data) | Needs checking | Controls that involve legal or financial commitments or modify data must be one of: (reversible, checked, confirmed). |
4.1.3 Status Messages | Needs checking | “status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus.” |
AAA standard
Not yet analyzed.