Per our previous discussion in the Quail API issue queue, Node Accessibility is unable to provide accurate line numbers in its reports. Given the difficulty in reporting line numbers which would be useful to the user in this context, I propose that you either a) eliminate the display of line numbers entirely from accessibility reports, or b) provide a configuration option to permit line numbers to be hidden. I believe that the current behavior (displaying line 0 for all items) is confusing to the user, who is already being provided with the correct HTML context in the report.

Comments

thekevinday’s picture

thekevinday commented
Assigned: Unassigned » thekevinday

I have been brainstorming on how to solve this.
This can be broken down into two approaches/issues:
1) Provide a new module, lets call it Field Accessibility Validator for the moment.
- This module will provide on the spot scanning button, or something like that, that can give the user immediate feedback before saving content.
- This could possibly even evolve into a validator such that they cannot save a node if the field fails some validation criteria.
- This approach would give accurate information in regards to the line numbering of the pre-renderred code; that is, accurate line number for everything in the text area.
2) Rework the logic in how I am handling the issue reporting.
- The current design uses quail libraries report results directly, which at best is quite ugly and at worst is entirely confusing to the user as noted by jerry.

With #1, I am going to have to spend a little time learning how to do this, but it should be do-able in a relatively short amount of time.
With #2, this should be simply but may take a bit of effort in time.
What I am going to hve to do with #2 is get the line number data and and grab that the actual marked up code myself and store than instead of using the markup code provided by quail library.
I am then going to have to provide some sort of view generated code screen and even do line highlighting.
I think the d6 equivalent module did something along these lines, so I could possibly use them as an example of what to do.

I am going to push out a new alpha version just to publish some of the current bugfixes.
After that I will begin working on this in hopes to get this released in the next alpha release.
This will be a significant change to do in an alpha release, but I do think I should add this before the final release.

thekevinday’s picture

thekevinday commented

I am going to take your advise of removing the line numbering from being displayed for the 1.x series (I will then push the stable 1.0 version out).

Then, I will at some point begin working on and adding this feature in the 2.x series that has yet to be started.

jerry’s picture

jerry commented

Excellent; thank you.

thekevinday’s picture

thekevinday commented
Status: Active » Fixed

Hmm, I've never closed this.

There has been a lot of work done with accessibility in drupal and they have taken over the accessibility project.
I don't think this issue will apply in the next version if/when it is created.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.