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

3.1.3 Unusual Words and neologisms/slang/made-up words #3591

Open
patrickhlauke opened this issue Dec 6, 2023 · 3 comments
Open

3.1.3 Unusual Words and neologisms/slang/made-up words #3591

patrickhlauke opened this issue Dec 6, 2023 · 3 comments

Comments

@patrickhlauke
Copy link
Member

patrickhlauke commented Dec 6, 2023

3.1.3 applies to

words or phrases used in an unusual or restricted way, including idioms and jargon

does this definition include neologisms, slang, and/or made-up words, like "flawesome" (which I admittedly only discovered today).

my gut feeling tells me that yes, it does cover it, because the SC normatively doesn't have any mitigation along the lines of "unless the word/phrase is confusing for everybody".

thoughts?

@patrickhlauke patrickhlauke changed the title 3.1.3 Unusual Words and neologisms/made-up words 3.1.3 Unusual Words and neologisms/slang/made-up words Dec 6, 2023
@mbgower
Copy link
Contributor

mbgower commented Dec 6, 2023

Draft response for review:
In the Working Group's opinion, the existing documentation can stand.

The normative wording of the SC is fairly broad and appears to include any word or phrase which may be difficult to understand or novel:

specific definitions of words or phrases used in an unusual or restricted way, including idioms and jargon

The Understanding document likewise notes the SC exists because some users with disabilities may find it difficult to understand nonliteral word usage and specialized words or usage.

Finally the wording of the general technique tests seem to entirely encompass the situations you suggest:

For each word or phrase used in an unusual or restricted way

For these reasons, it does not seem necessary to adjust the guidance for this AAA SC. However, if you want to suggest an addition to either the technique or Understanding document to make this inclusion explicit, you are welcome.

@bruce-usab bruce-usab self-assigned this Dec 8, 2023
@patrickhlauke
Copy link
Member Author

@alastc
Copy link
Contributor

alastc commented Jan 26, 2024

Patrick would like to add some explicit mention of this for future testers, Pat to create PR.

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

No branches or pull requests

4 participants