-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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 manual audit to a11y to remind people to check for link states #5667
Comments
cc @robdodson |
That seems like a good idea to me :) Maybe for now we would just need to add a snippet in there explaining why this is important and how to check for it. |
Wow, now I'm talking to @robdodson. You and @paulirish have been heros' of mine for like 15 years. I've been learning from your work and blog posts my whole career. I can't tell you how cool it is submit an idea and y'all think its a good idea. Enough gushing. For Documentation, do you want me to write up a paragraph in Key Points and do a pull request here?https://github.com/google/WebFundamentals/blob/master/src/content/en/fundamentals/accessibility/how-to-review.md Or does @robdodson just want to take it from here? For Lighthouse, should I do the same and do a pull request? Or are we just adding it to documentation? |
Adding a paragraph to key points would be great. Then in Lighthouse we
could link to the heading for that section in the doc, similar to how we do
for the other manual audits.
…On Mon, Jul 16, 2018 at 7:43 AM joelhsmith ***@***.***> wrote:
Wow, now I'm talking to @robdodson <https://github.com/robdodson>. You
and @paulirish <https://github.com/paulirish> have been heros' of mine
for like 15 years. I've been learning from your work and blog posts my
whole career. I can't tell you how cool it is submit an idea and y'all
think its a good idea.
Enough gushing.
For Documentation, do you want me to write up a paragraph in Key Points
and do a pull request here?
https://github.com/google/WebFundamentals/blob/master/src/content/en/fundamentals/accessibility/how-to-review.md
Or does @robdodson <https://github.com/robdodson> just want to take it
from here?
For Lighthouse, should I do the same and do a pull request? Or are we just
adding it to documentation?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5667 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABBFDYdpixjCQe_ym-qXXuFj7BzpWKW8ks5uHKapgaJpZM4VPZ_5>
.
|
@joelhsmith great idea! Feel free to create a PR here. The text part can be reviewed by the team when the PR is created. |
@wardpeet Thanks! So far I wrote up some text for the Web Fundamentals How to Review page and made a PR that was approved by @robdodson. Now that there would be a corresponding page for the 'Learn more' link, I would like to submit a manual audit to Lighthouse that incorporates @robdodson 's text improvements. I will submit a PR this week for my proposed manual audit. |
Awesome looking forward to it! |
Can we add a manual accessibility audit to remind people to check that links and buttons are distinguishable from adjacent text and have perceivable hover states.
Here is a conversation starter:
I understand we probably don't want to link to a webaim blog post, so we probably need to add a page here:
https://github.com/google/WebFundamentals/tree/master/src/content/en/tools/lighthouse/audits
I am willing to do the work, if there is interest.
The text was updated successfully, but these errors were encountered: