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

remove overly prescriptive distinctions from aria-current values. #1660

Merged
merged 3 commits into from
Aug 30, 2022

Conversation

cookiecrook
Copy link
Contributor

@cookiecrook cookiecrook commented Dec 10, 2021

Resolves #1656.


Preview | Diff


💥 Error: 504 Gateway Timeout 💥

PR Preview failed to build. (Last tried on Jun 24, 2022, 8:22 PM UTC).

More

PR Preview relies on a number of web services to run. There seems to be an issue with the following one:

🚨 Spec Generator - Spec Generator is the web service used to build specs that rely on ReSpec.

🔗 Related URL

<html><body><h1>504 Gateway Time-out</h1>
The server didn't respond in time.
</body></html>

If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.

@cookiecrook
Copy link
Contributor Author

Note: I also removed overly prescriptive context limitations on the other values (e.g. location was limited to an "image" in a "flow chart"), so this is a little more than editorial.

@scottaohara
Copy link
Member

I'm glad you made that change... i personally never interpreted that bit about location to mean that was its only use case. Especially since that listing is preceded by the words "for example".

Was it really a normative limitation being set there? That might be a gap in my understanding on how normative declared examples are if they are not contained within notes or non-normative sections

@carmacleod carmacleod self-requested a review December 16, 2021 18:23
Copy link
Contributor

@carmacleod carmacleod left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

2 comments (in suggestions below):

  1. I really do prefer "set of pages" in the first suggestion below, because "page-based process" feels overly prescriptive. ;)
  2. Just something to think about with "location" instead of "component" in the second suggestion below, but I think it's fine either way.

index.html Outdated Show resolved Hide resolved
index.html Show resolved Hide resolved
@pkra pkra added this to the ARIA 1.3 milestone Jan 12, 2022
Co-authored-by: Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com>
@pkra pkra self-assigned this Aug 25, 2022
@jnurthen jnurthen merged commit 72063a0 into main Aug 30, 2022
github-actions bot added a commit that referenced this pull request Aug 30, 2022
)

SHA: 72063a0
Reason: push, by @jnurthen

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
pkra pushed a commit that referenced this pull request Aug 31, 2022
)

Co-authored-by: Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com>
jnurthen pushed a commit that referenced this pull request Oct 10, 2023
)

Co-authored-by: Carolyn MacLeod <Carolyn_MacLeod@ca.ibm.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Suggest change to aria-current step (not only a link)
6 participants