-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Focus Appearance and Alt Text outcomes first draft #112
Conversation
Content taken from [Focus Appearance (Exploratory to Developing)](https://docs.google.com/document/d/1H5Fk9QRy6WutIUyrCRcqXH04mkp2EFq_qeRXvMawWf0/edit?usp=sharing)
✅ Deploy Preview for wcag3-howtos ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi! Couple of things to check in here - For Focus appearance:
For Text alternatives:
|
I feel you are heading in right direction. In particular, it is helpful to now have outcome Focus Appearance as a more realized model Keyboard Input to follow. |
We need to rework this to better reflect the realignment of guidelines, outcomes and methods discussed in today's meeting. |
Hi, folks, thanks so much for all of the great work on this so far! I huddled with a few members of COGA, and we have some flags about the outcome template/formatting: Hierarchy of informationOutcome name (“Focus appearance”) is hard to notice at the top of the page.
“Get started” sounds like a second step (“Take action/What to do”) instead of first step (“Purpose/Why to do it).”
Box just below “Get started” needs more context to connect it to the rest of page.
“Methods” page would benefit from a tweak that makes two things clear:
“User needs” seems like it should come before “Methods” One page vs many tabsThe current template has a lot of tabs.
ColorsRed
Light blue/gray
Breadcrumb formattingRight now there is no visual emphasis to help users what page they’re on.
|
Question on Prerequisites being presented prior to baseline or enhanced and use of overall use of these words. A numbered list shows that an enhanced option precedes a prerequisite whereas the defined term of prerequisite is either a thing that is required as a prior condition for something else to happen or exist. or required as a prior condition.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just some comments for my first pass through.
some comments aren't scoped to the content of the drafts, but some of the markup being used to signify the pages are drafts.
probably need to do a few more reads of this to make sure i don't have other thoughts.
2. Replace it with the text alternative. | ||
3. Check that the meaning is substantively equivalent | ||
1. the purpose of the non-text content is met by the text alternative. | ||
2. The way the content is presented is using the most appropriate, accessibility-supported (math, code samples, etc.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i don't quite follow this point. maybe because it reads as an incomplete sentence?
✅ Deploy Preview for wcag3 ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
…c/wcag3 into alt-text-and-focus-appearance
Co-authored-by: Scott O'Hara <[email protected]>
Separating to another branch.
…c/wcag3 into alt-text-and-focus-appearance
Clear meaning
Content taken from Focus Appearance (Exploratory to Developing) and Text Alternatives (Exploratory to Developing)