/WAI/site/authoring-tools

From W3C Wiki

Authoring Tool Material IA & URI

What ATAG-related resources do we envision in the next few years?

  1. ATAG Report Tool
  2. Authoring Tools List
  3. Update Selecting and Using Authoring Tools for Web Accessibility <https://www.w3.org/WAI/impl/software>
  4. ? other ?

We need to figure out for ATAG Report Tool (ART) now, and would be good to think of other potential material while we're at it.

IA (information architecture)

Each resource will have a single primary home in the IA. We can link to the resources from multiple places.

Report Tool - IA

Proposal: Its primary home is under Evaluating Web Accessibility / Conformance Evaluation and Reports (on these pages: https://www.w3.org/WAI/test-evaluate/#conformance & https://www.w3.org/WAI/test-evaluate/conformance/ )

  • Test & Evaluate
    • Evaluating Web Accessibility Overview
    • Easy Checks - A First Review of Web Accessibility
    • Evaluation Tools
      • Selecting Web Accessibility Evaluation Tools
      • Web Accessibility Evaluation Tools List
    • Conformance Evaluation and Reports
      • WCAG-EM Overview: Website Accessibility Conformance Evaluation Methodology
      • WCAG-EM Report Tool: Website Accessibility Evaluation Report Generator different format
      • Template for Accessibility Evaluation Reports
      • ATAG Report Tool
    • Using Combined Expertise to Evaluate Web Accessibility
    • Involving Users in Evaluating Web Accessibility

Considerations:

  • + pro: it's with WCAG-EM Report Tool
  • - con: ART has much smaller, specific audience, and having it on general Evaluation page adds more complexity to that page
    (yet +1 for increasing visibility of ATAG :-)

Input:

  • Shadi: ... like the IA proposal to put together with the WCAG-EM Report Tool as part of "[conformance] evaluation".

Option 2: Standards/Guidelines / ATAG (https://www.w3.org/WAI/standards-guidelines/#atag) -- Shawn thinks not home it here, and of course, add clear links to it from that page, https://www.w3.org/WAI/standards-guidelines/atag/ , and other relevant places.

List & Selecting Tools - IA

Straw Proposal: Under Planning & Policies / Authoring Tools (new sub-heading) as follows:

  • Planning & Policies
    • Planning and Policies Overview
    • Web Accessibility First Aid: Approaches for Interim Repairs
    • Planning and Managing Web Accessibility
      • Initiate
      • Plan
      • Implement
      • Sustain
    • Developing Organizational Policies on Web Accessibility
    • Developing an Accessibility Statement
    • Authoring Tools
      • Authoring Tools List
      • Selecting and Using Web Authoring Tools for Accessibility
    • Involving Users in Web Projects for Better, Easier Accessibility
    • International Laws & Policies

Considerations:

  • +pro: good visibility
  • -con: 8 top-level categories is pushing the usable limit

Option 2: Under Planning & Policies / Planning and Managing Web Accessibility / Authoring Tools (new sub-heading) — that is,

  • Planning & Policies
    • Planning and Policies Overview
    • Web Accessibility First Aid: Approaches for Interim Repairs
    • Planning and Managing Web Accessibility
      • Initiate
      • Plan
      • Implement
      • Sustain
      • Authoring Tools
        • Authoring Tools List
        • Selecting and Using Web Authoring Tools for Accessibility
    • Developing Organizational Policies on Web Accessibility
    • Developing an Accessibility Statement
    • Involving Users in Web Projects for Better, Easier Accessibility
    • International Laws & Policies

Considerations:

  • -con: poor visibility
  • -con: extra complication to integrate with main Planning and Managing Web Accessibility resource pages

Option 3: Under Standards/Guidelines / Authoring Tool Accessibility Guidelines (ATAG) Overview

URIs

Note: With the 2018 redesign, many URIs were changed, and not everyone likes it. At some point, Shawn hopes to go back to simpler URIs for most pages. Standards overview pages were at WAI/intro/xxag — and will probably change to /WAI/xxag/Overview.html

Related URIs:

  • Authoring Tool Accessibility Guidelines (ATAG) Overview was at /WAI/intro/atag (now at /WAI/standards-guidelines/atag/)
  • ATAG at a Glance was at /WAI/intro/atag-glance (now at /WAI/standards-guidelines/atag/glance/)
  • Old resource "Selecting and Using Authoring Tools for Web Accessibility" was at <https://www.w3.org/WAI/impl/software>.
    /WAI/impl/ was short for /WAI/implementing and was the precursor to /WAI/planning/ , /WAI/planning-and-managing/
  • WCAG-EM Report Tool URI is https://www.w3.org/WAI/eval/report-tool/

Proposal: Create 2 new top-level directories:

  • /WAI/authoring-tools/
    • Selecting and Using Web Authoring Tools for Accessibility
    • Authoring Tools List
    • ATAG Report Tool
  • /WAI/atag/ (do this later when change 2018 URIs)
    • Authoring Tool Accessibility Guidelines (ATAG) Overview
    • ATAG at a Glance

Option 2: Put all 5 resources under /WAI/authoring-tools/

  • Shadi: wondering about "WAI/authoring-tools" vs "WAI/authoring" only?
    • Shawn: I think WAI use of "authoring" in several contexts covers things like content development. So, then would all of the design and development resources would fit under there? Anyway, I'm inclined not to go there now. Can revisit when we look at overall URIs.

Option 3: Put all 5 resources under /WAI/atag/

  • Judy: My own strong preference is for short, e.g. option 3:
    • Shawn relies:
      • I also generally support shorter. (And do have getting back to the old, shorter URIs on my To Do list, albeit very low priority.)
      • My hesitation with that it is: Do we really want all our authoring tool work to be under a specific guidelines acronym?
      • I think the "Authoring Tools List" and "Selecting and Using Web Authoring Tools for Accessibility" should be under a broader URI, rather than /atag
        • Judy: Ideally, yes, but most of the appropriate longer ones seem unnecessarily long.
      • Note also Shadi's comment: "I also like the URI idea of "WAI/authoring-tools" to give authoring tools a home independently of ATAG."
        • Judy: For typing URIs, which sometimes one has to, the hyphenated "authoring-tools" can trip one up.
      • Judy, do those considerations change your strong vote for Put all 5 resources under /WAI/atag/ ?
        • Judy: Unfortunately not really.

Another option 4: Put ART under /WAI/eval/atag-report-tool/

  • Shadi: ... like the IA proposal to put together with the WCAG-EM Report Tool as part of "[conformance] evaluation". Consistent with this, I mildly like URI option 4, to put it under "eval/atag-report-tool" (we could move the WCAG-EM Report Tool to "eval/wcag-report-tool" or such with the next release). At the same time, I also like the URI idea of "WAI/authoring-tools" to give authoring tools a home independently of ATAG. Regardless of where the tool lives, we will need good and clear cross-referencing from both places in the IA, so I don't feel really strongly about the URIs especially since you are redesigning them.
Conclusion: Go with /atag/ because Judy feels strongly. Shawn doesn't have energy to debate any more. Shadi thinks unfortunate.

(W3C Team - Current WAI directories: https://edit.w3.org/WAI/CVS?action=showdirs )