Comments (5)
you beat me there by 5 minutes...was just about to push up a PR 🏃
from wcag.
Well, you took that merge conflict off my hands, so I had a little time to look at something else
from wcag.
As noted in the PR, I have located the original official WG response showing that this was clearly intended to be an appendix.
Given the wording of 5.1, an acceptable solution is also simply to add the word "Appendix" to the heading.
Introductory material, appendices, sections marked as "non-normative", diagrams, examples, and notes are informative (non-normative).
That said, I think it would be good to see if there's anything in a style guide that shows how appendices are supposed to be structured, and make sure we follow that. Some may argue that the sections labelled with letters in our document are the indicators of appendices (again, with no label). @shawna-slh @iadawn are you aware of any guidance on this?
My old copy of Chicago states:
When more than one appendix appear in a book, they should be numbered like chapters (Appendix 1, Appendix 2, etc.) or designated by letters (Appendix A, Appendix B, etc.), and each should be given a title as well.
from wcag.
It has been pointed out that WCAG 2.0 is significantly different than WCAG 2.1 in regard to structure, with each appendix specifically named and grouped under an Appendices section following the (unnumbered) conformance sections.
WCAG 2.0
WCAG 2.1
WCAG 2.1 introduced a right navigation for the outline. This may have contributed to changes in visible structure, but to point out some obvious differences, the glossary was previously (and problematicly) in an appendix BUT also marked normative. In 2.1, the glossary was moved forward (and its enumeration changed from a letter to a number), but while some Acknowledgements and References remained lettered B and C, all references to appendices vanished.
from wcag.
My suggestion from the meeting:
Add the appendix heading about change log, and mark those and appendix a/b/c. (Probably done with the respect based classes rather than in text.)
Leave section 7 as it is (removing transction-amount separately), and it essentially is normative by that marking, removing the ambiguity.
from wcag.
Related Issues (20)
- Is the assumption behind technique F87 still valid (meta issue) HOT 11
- Add section in Understanding of WCAG2,2:2.5.8 for vertical menus HOT 9
- WCAG Abstract section makes distinction between "tablets" and "mobile devices" HOT 12
- Success Criterion 1.4.5 Images of Text - Image of text + visual real text that matches the content of the image HOT 7
- Old and new dialog techniques aren't showing correctly HOT 1
- Contrast understanding docs (1.4.3, 1.4.6, 1.4.11) need guidance on when to use pixel-picking HOT 2
- Technique F110: Add screenshots to help the user see examples HOT 3
- Clarification regarding success criterion 2.2.2 Pause, Stop, Hide concerning prefers-reduced-motion HOT 11
- Media queries and alternate versions HOT 2
- S
- Broken image in failure F69 HOT 2
- 1.3.1 / F87 for input fields with mandatory visual indication via pseudo-element HOT 4
- 1.4.3 / 1.4.11 Meeting contrast requirements via conforming alternate versions? HOT 4
- 1.4.4: Resize text: acceptability of a "link to a full version" HOT 8
- Technique F91: Related techniques are wrong HOT 1
- Technique F95: Realated technique SCR39 missing
- Technique F82: Add 3 references under Related techniques HOT 2
- Technique F86: Add related technique ARIA14
- Technique F97: Add related technique G214 HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wcag.