v.0.6.2

Bug fixes

• Make active link environment aware.

Minor changes

• Fix release process for GitHub pages (includes creating symlink for 404.html to index.html during build, so that SPA routes work)
• Fix URIs for icons in pager links

v.0.6.0

Minor tweaks

• Add “Not Checked“ total to listing (#158) and to categories (#157)
• More semantic markup (#160)
• Place navigation over full width of grid (#162)
• Add footer, help improve and acknowledgements (#156)
• Add basic styles to table in HTML output (#165)

Bugs fixed

• Improve Internet Explorer 11 support (#119)

v.0.5.0

Tweaked “Your Report” box

• The “Your Report” box now shows progress (in %, visualised as a progress bar) for the report, and split out per Principle (#60)
• It's no longer different on the About page
• The “Cancel” button is now “Start a new report” as that makes more sense from a user perspective
• The box can be collapsed, so that more space is available for the main content

HTML export (#72)

• You can now export a report to HTML.
• The HTML version is an as simple as possible HTML document. It includes a heading, a summary and the full results in a table (see also #144, #145, #146, #147 and #148)

Improved Start page

• Updated links to Markdown (#136)
• Frontloaded information that is useful for all, put information for first time / new users into expand/collapse (#126)

Improved About page (#134)

• Updated description of “Report Identifier”
• Updated organisation with three headings.
• Changed Overview to About
• Changed Name to Name of Tool (#149)

Improved Report page (#132)

• Summary with totals available per result category (Passed, Failed, Cannot Tell, Not Applicable).
• Success criteria that were not checked are listed so that it is easy to find what's missing.

Bug fixes

• Better support in Internet Explorer 11 (both CSS and JavaScript support) (#119)
• Link between report and SCs improved (#138)

0.4 Draft

This is an overview of what has changed since the last release.

Support for multi-level SCs (see #95)

Some Success Criteria in ATAG (those that correspond to WCAG criteria) can be evaluated as one of 3 levels (A, AA, AAA). The ATAG Report Tool now lets users choose which level to evaluate as, and displays that level on the report page.

Colour coding of result options (see #93)

In the Report page, results now have a colour indication to aid scanning.

“Download as HTML” added

A first version of “Download as HTML” is now in the tool, with some known issues.

Updated evaluation box (see #60)

• Less focus: moved to right of page (large viewports) / bottom of page (small viewports) / lower in source order (assistive tech)
• “Clear” button is now “Start new evaluation” as that implies clearing and better matches user expectation
• Consistently talks about “report” instead of “evaluation”
• Better counting of totals (see #114)

New fields (see #65)

Both of these new fields can be edited on the Report page.

Report identifier

This unique reference is the date by default, but it can be changed to anything else.

Executive summary

This field can be used to provide a summary of the report. Markdown is enabled.

Content tweaks

• First page changed to more clearly separate between background info and main info (tips moved to top) (#126)
• Now all fields show up in Report, even if not provided (then “Not provided” is displayed instead of nothing) (#71)
• Page titles for principles are much closer related to ATAG principles (#58)
• Better wording for “legend of results” (#83)
• Better field names (#66)
• We now have a URL field for authoring tool (#52)

Visual tweaks

• Changed visual design of Implementing links and made consistent with Principle links (#69)
• New header with name of tool displayed at top, “ATAG Report Tool” removed from individual page headings (#23)

Bugs fixed

• Implementing links not generated consistently (#85), sent to working draft instead of TR (#124)
• Tool did not work at all in Internet Explorer 11, added basic support
• JSON download did not work in some browsers (#86 and #91)
• Better tab order in SC (#77)
• Default choice was not always default, sometimes it showed as Passed (#84)

0.3 Draft

This is an overview of what has changed since the previous version.

Import functionality

With the “Import” button, users can now import a previously exported JSON file for an evaluation.

Markdown support

Observations can now be added in Markdown. There is a link to preview with each field, it links to the part of the results page that includes a preview of the observation.

Other

Other features:

• You can add the URL of an authoring tool under “Your evaluation”
• The Start page has “Expand all” / “Collapse all” buttons

0.2 Draft

This is an overview of what has changed since the previous version.

Updated header and navigation

We now use the WAI simplified header, which is also used in the WCAG EM Report Tool and the Authoring Tools List prototype. It is short, contains minimum content and reinforces you're on a WAI site.

Navigation was updated, too. It was vertical, it is now horizontal and integrated with the header.

New component: evaluation box

Assumptions are that:

• Users of this tool will be doing multiple evaluations, maybe in the same week, especially so if they are a professional accessibility evaluator
• We store an evaluation locally on the user's computer (as requested in #26). We think this is useful, but realise it could be confusing.
  • Note: it is listed in the Note on the front page, but we can assume not everyone will read
• It is generally useful for evaluations to have names (and this was a comment in the previous survey)
• People might want to go back into an evaluation they did previously, for re-evaluation or maybe to adjust a comment or result

Following this, the user need is: as an accessibility evaluator, I want to have easy access to what my current evaluation is, so that I can feel confident about what I am

Suggested new element to help with this: the evaluation box.

• It is dynamic. If you are new into the tool, it suggests to start a new evaluation or import. if you have a locally saved version, it displays the name of that version and has option to Save or Clear. (In WCAG EM Reprt Tool, all those options are always available; this makes them contextually available)
• It displays in real time how many success criteria you've evaluated ('evaluated' means you have selected some option for that SC)
• On desktop it floats on the left, on mobile it is on the top of the page.
• It is meant to give users confidence about which evaluation they are currently working on (probably always helpful, but especially helpful when doing evaluations for multiple clients/projects). This is similar functionality to Google Docs displaying name of doc prominently.
• It is meant to help people understand if they're in a previously saved evaluation versus a new one

Updated start page

Content on the start page was updated in #34, to be more to the point and include a list ('legend') of the different evaluation results.

Evaluation saved locally

Requested in #26, evaluation is now saved locally, so that it is still there when someone presses 'Refresh'. This uses browser localStorage and availability depends on various factors (browsers may clear it to save space or in certain privacy settings).

Results rendered

Results are now available in HTML in the last 'step'.

Your Evaluation page added

Users can now add meta info like their name and the name of the tool. This is a minimal first version, it may be all we need, or we may need more fields.

Bugs / tweaks

• issue #31 (empty notes were displayed)
• issue #27: “not applicable” added as evaluation result