alphagov / wcag-primer Goto Github PK
View Code? Open in Web Editor NEWGet up to speed with the Web Content Accessibility Guidelines
Home Page: https://alphagov.github.io/wcag-primer/
Get up to speed with the Web Content Accessibility Guidelines
Home Page: https://alphagov.github.io/wcag-primer/
In the '2.5.4 Motion Actuation' section of the 'All requirements' page, one of the requirement and all of the resources relate to honouring users' preferences for reduced animation motion:
Use the new prefers-reduced-motion CSS declaration. This will detect if the user would like to reduce animation or motion on the pages they visit.
Those are not within the scope of SC 2.5.4 'Motion Actuation'. They fall under SC 2.3.3 'Animation from Interactions', which is out of scope for this guide as it's AAA-level..
1.3.2. Meaningful sequence, together with its description, appears twice in a row.
https://alphagov.github.io/wcag-primer/all.html#1-3-2-meaningful-sequence-a
The checklist questions for 2.5.1 and 2.5.4 describe the precondition for the tests, but not the expected outcome:
I believe that the expected outcome for 2.5.2 should be the opposite of what the question suggests. (i.e. The functionality should not be triggered the moment on the down event).
On the overview page, the summary of Success Criterion 2.4.6 currently tells readers to "provide headings and labels":
Provide headings and form labels that will help people find content and complete tasks.
But in fact, WCAG SC 2.4.6 doesn't require headings and labels to be provided (that's covered by 1.3.1 and 1.4.2). It only says that headings and labels that are provided must accurately describe topic or purpose:
2.4.6 Headings and Labels: Headings and labels describe topic or purpose. (Level AA)
So, not using labels or headings is not a violation of 2.4.6. What is a violation of 2.4.6 is using labels or headings that don't correctly describe the topic of their associated section or input.
The summary of 2.4.6 in the 'All requirements' page gets that right:
Headings must indicate the topic or purpose of the content in that section of the page, and labels must indicate the purpose of the field they relate to.
The overview of 1.4.13 Content on Hover and Focus stats with ...
This is for mobile or tablet devices - ...
I don't believe that SC 1.4.13 is just or mobile or tablet users. Parts of it are for mouse and desktop-type screen reader users too.
I believe that "This is for mobile or tablet devices -" should be removed.
The explanation of 'path-based gesture' currently reads:
"If an interaction is not just the end-to-end part but important but also the road or path taken. These gestures could be swiping, dragging items or drawing."
That sentence is not clear.
The issue is both on the index page and on the details page for 2.1.1.
I have submitted a pull request to fix it: #34
"Make sure every task can be completed without a mouse."
This doesn't work as an accurate summary of the success criterion, because:
I propose rephrasing the summary to:
"Make sure every task can be completed using just a keyboard."
"It must be possible for someone using a keyboard or touch device to complete all tasks in a service. This ensures that people with mobility impairments who do not use a mouse can successfully complete their goals."
"Requirements / What to do?
This is confusing in the same way. It suggests that if a user can complete tasks using a touch screen device, the success criterion is met. But in the official W3C WCAG, this success criterion is not about touch screen at all.
I suggest rephrasing the intro paragraph to this:
"It must be possible for someone using only a keyboard (or a device that emulates keyboard commands) to complete all tasks in a service. This ensures that people with mobility or dexterity impairments who do not use a mouse can successfully complete their goals."
I also suggest deleting the second requirement about touch-screen device.
The overview summary of Success Criterion 1.4.10 'Reflow' currently reads:
Where content is zoomed there should be no loss of information or functionality. In particular on smaller devices or resolutions of 320px (vertically) or 256px (horizontally) there should be no scrolling in two directions when resized.
When I read this, it took me a while to understand what '320px (vertically)' and '256px (horizontally)' meant. I interpreted it as:
But that interpretation is incorrect as per WCAG Success Criterion 1.4.10:
- Vertical scrolling content at a width equivalent to 320 CSS pixels;
- Horizontal scrolling content at a height equivalent to 256 CSS pixels.
We should clarify and remove the misleading ambiguity.
The requirements for the 'hoverable' part of 1.4.13 Content on Hover and Focus say to:
Manage focus and move the mouse pointer directly from the trigger onto the new content.
I don't understand what 'manage focus' means in the context of making an element hoverable.
It sounds like "manage focus" refers to managing keyboard focus.
Note: I'm reporting all these issues because I believe that this doc will be very useful to many people once it's finalised.
On the document issues wiki page, there is a link to a spreadsheet which isnβt publicly viewable:
Richard Morton's WCAG 2.0 accessibility testing template (XLSx) - note this is based on an older version of WCAG)
It would be nice if this was publicly viewable β or if this is intentional, maybe add a "(access restricted)" note?
A heading for Guideline 2.5 Input Modalities is missing on this page:
https://alphagov.github.io/wcag-primer/index.html#guideline-2-4-provide-ways-to-help-people-navigate-and-find-content
Success Criteria 2.5.1 to 2.5.4 are listed under Guideline 2.4.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. πππ
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google β€οΈ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.