web staff : report; more accessibility info

Signed-off-by: Bill Erickson <berick@esilibrary.com>

diff --git a/web-staff-report.txt b/web-staff-report.txt
index f83fe79..2e8ac73 100644 (file)
--- a/web-staff-report.txt
+++ b/web-staff-report.txt
@@ -142,14 +142,25 @@ Two Items of Note
 Accessibility / Screen Reader support
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-* Use of labels, titles, alt text, etc. as necessary.
-* Basic tests were performed with 
-https://addons.mozilla.org/en-us/firefox/addon/fangs-screen-reader-emulator/[Firefox Fangs Screen Reader Emulator]
-
-Of all the dev goals, this is the one I have the least confidence in
-for the prototype, simply because of my lack of experience.  Further
-research is under way, but the code would benefit from community review, 
-live screen reader testing, etc. before any more development occurs.
+Browser-based applications have access to a number of accessibility
+features out of the box, like true global font scaling, page zooming,
+search-in-page, full-text history searching, and broad support for
+assistive technology software, like screen readers.
+
+Ensuring that the application is developed in such a way that all such
+features may be used to their fullest potential is up to us.  The
+prototype takes simple steps, like applying labels, titles, alt tags and
+attributes as necessary, but there are larger tasks to address before
+full-blown development ensues.  For example, reviewing the CSS to allow
+for high-contrast themes, support for cursor-based navigation, and
+keyboard shortcuts, to name a few.
+
+Additionally, basic tests were performed against the prototype using 
+https://addons.mozilla.org/en-us/firefox/addon/fangs-screen-reader-emulator/[Firefox Fangs Screen Reader Emulator].  Fangs produced the expected output, in as much as it 
+was able to produce the correct textual values in the expected structure, 
+but the interface would clearly benefit form further community review and 
+live screen reader testing, etc. as we look ahead to designing the best
+information structure and flow for assistive software.
 
 Quality Assurance Testing
 ~~~~~~~~~~~~~~~~~~~~~~~~~