Skip to content
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

tagline/strapline wording #93

Open
shawna-slh opened this issue Mar 22, 2022 · 0 comments
Open

tagline/strapline wording #93

shawna-slh opened this issue Mar 22, 2022 · 0 comments
Assignees

Comments

@shawna-slh
Copy link
Contributor

shawna-slh commented Mar 22, 2022

image

Background from #86 (comment):

SLH: Yes, per below, it’s important for others that this type of info be in the header.

WF: We're not clear on the "For developers of evaluation tools and test methodologies" phrase. Is the intent for each page to have the target audience identified in the header? If so we want to discuss this in more details. We briefly talked about "Accessibility testers and test writers", but haven't settled.

SLH: It’s important that “not required to meet WCAG” is front and center for techniques and supplemental guidance and understanding. It is now in the header. e.g.:
"Supplemental Guidance to WCAG 2
Additional ways to improve accessibility (not required to meet WCAG)"

It seems for Rules, the important relevant bit communicates: If you landed here from a search engine, you’re probably not where you want to be. This is for developers of evaluation tools and test methodologies. …
I suggest we open a new issue to work on wording for this.

From #86 (comment)

WF:

"For developers of evaluation tools and test methodologies"
-> "For accessibility testers and developers of test tools and methodologies"
I think the current wording is too specific. ACT rules are written for anyone doing testing.

SLH: Would be nice to keep this to one line, not wrapping, on common configurations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants