-
Notifications
You must be signed in to change notification settings - Fork 36
Hackday #13
- Josh Muheim (Access4All)
- Esther Brunner (Zeix),
- Donato Rotunno (Liip)
- Nicolas Ricklin (Liip)
- Thomas Jaggi (früher Unic),
- Jürgen Rudigier (Hinderling Volkart)
- Luc Guillemot (Interactive Things)
- Graciela Schütz (Unic)
Josh presents the new WCAG 2.1, retrospecting the 1.0. and 2.0 (the later is still current).
- Released June 2018
- Backwards compatible (new additions to the 2.0)
- Speech recognition (like Siri, Alexa)
- 1 new guideline
- 17 new success criteria (A: 5, AA: 7, AAA: 5)
Josh presents a visual map of the new WCAG 2.1 by Intopia, WACAG 2.1 Visual Map by Intopia
New additions:
Content needs to adapt to the content (landscape or portrait). A4All evaluates this with the browser developer tools to simulate mobile devices.
Form fields need proper autocomplete attribute, there are 53 input purposes as possible values found here WCAG 2.1 Input Purposes A4All evaluates this by inspecting with e.g. manual code inspection, Chrome auto-fill (or similar), Web developer toolbar (displaying form details), or automatically by script (new idea).
Content must adapt to the viewport (reflow), no need to scroll in two dimensions in the same container and content isn't overlapped. Exceptions are images, maps, diagrams video, games and data tables. A4All evaluates this with the browser developer tools to simulate mobile devices, and inspects visually if there are overlapped content.
Contrasts of non-text-context must be 3:1 e.g. (field-input frame-lines, frame-lines, graphical objects, icons) Objects don't necessarily need a border,, as long as the are perceivable as intended (e.g. buttons is perceived as a button). Hover states doesn't need to have any additional contras requirements.
Text dimensions need to be adaptable to at least without clipping or horizontal scrolling, no overlapping texts (exceptions e.g. video subtitles, pdf's).
Content that appears as the result of a hover or keyboard needs to be controllable by the user. (not overlapping with other contents, no clipping, and they must be dismissible). Evaluation by manual inspection.
Single character key shortcuts must be configurable to remap them or to be turned off. Due to voice-recoginition or to screen-readers softwares.
For complex gestures provide simple alternates to interact with content, most relevant for mobile apps. Evaluation by manual inspection.
Pressing on a target (down-event) must be cancellable or reversible (don't tigger actions on down-event). Evaluation attach script to a key down event.
Visible labels must match or are include accessible name of labels (use elements, don't use aria-label or aria-labelledby, alternative texts of symbols, visually hidden parts of text). Speech input users navigate by speaking the visible labels. Bad examples are labelling a button with "Find in this site", and the text of the button is "Go" (for a search-button), for more bad examples see Bad ARIA Practices Evaluation today, manually inspection through all the labels or with help this tool ANDI Accessible Name and Description Inspector accessibility testing tool.
Motion activated can also be operated by more conventional user interface components.
Using ARIA role=alert or Live Regions to identify errors. For best practices see: Noticing Screen Readers Using Alert Role
- Adding more content what the WCAG 2.1 is. Together with the Swiss Administration A4All produced in the past the accessibility checklist found here Accessibility Checklist. Now is the idea to add a new part WCAG 2.1 to the ADG (so that maybe it can be referenced by other official sites). See issue here New part "WCAG 2.1"
- Adding new videos like this examples Headings outline of myswitzerland.com, Headings outline of airbnb.com
It was mentioned, that the content should be splitted from the rendering engine. This will be a major refactor of the ADG, so it was questioned if it would not be easier to relaunch it with a new design implementing a future vision. A new ticket for this discussion was opened Split content from presentation repo
- 7.4.2020 @Zeix, Badenerstrasse 65, 8004 Zürich. Topic "Mobile Screenreaders"
- 16.6.2020 @Unic, Belpstrasse 48, 3007 Bern. Topic "ADG Strategy" (Target Groups, Vision)