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

success criteria names #15

Open
nitedog opened this issue Jun 16, 2014 · 3 comments
Open

success criteria names #15

nitedog opened this issue Jun 16, 2014 · 3 comments

Comments

@nitedog
Copy link

nitedog commented Jun 16, 2014

Page: first page under "browse test results"
Issue: use only the handles for principles, guidelines, and success criteria:

Principle 1: Perceivable

  • 1.1: Text Alternatives

    -- 1.1.1: Non-text Content

Note: you /could/ link these handles to the corresponding sections in WCAG 2.0 (with the "opens in new window" icon used elsewhere on the page)

@evlach
Copy link
Member

evlach commented Aug 12, 2014

@yatil could you give me the xpath from https://raw.githubusercontent.com/w3c/wcag/master/wcag20/sources/wcag2-src.xml

these are the xpaths I use now;
principles = "//div2[@ROLE='principle']"
guidelines = "./div3[@ROLE='group1']"
criteria = "./div4[@ROLE='req' or @ROLE='bp' or @ROLE='additional']/div5[@ROLE='sc']"

not clear to me what we are looking for.. I mean given that we want to extract automatically..

@yatil
Copy link
Contributor

yatil commented Aug 13, 2014

Ah, it’s bonkers that they are not broke up in more granular pieces of information. Basically, @nitedog wants to have the principles without the parts after the dash (I think that could be easy to parse, but I don’t know.

I have now idea if we can solve the guidelines part, as there are no short name in the document at all, which would be useful. The criteria is fine as is.

(BTW: I’m against having links to the individual techniques there, adds only clutter. We could add an informational text with a link to WCAG above the filters, if really, really, really needed.)

@sharronrush
Copy link

@nitedog Request to close - is this issue resolved?

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