Conversation
Add export HTML to it's own branch
| <tbody> | ||
| <tr> | ||
| <th>ARIA Specification</th> | ||
| <td><a class="core-mapping" href="#role-map-row">Role: `row not inside treegrid`</a></td> |
There was a problem hiding this comment.
| <td><a class="core-mapping" href="#role-map-row">Role: `row not inside treegrid`</a></td> | |
| <td><span class="el-context"><a class="core-mapping" href="#role-map-row">Role: `row` not inside `treegrid`</a></span></td> |
There was a problem hiding this comment.
In this case I don't think the element needs more context, which is why we're using this class. The corresponding core-aam sections disambiguates it, you actually have row inside treegrid and not inside treegrid
There was a problem hiding this comment.
So, @zakkinsey - based on Daniel's comment, we should not apply the suggestion and keep the original, right?
There was a problem hiding this comment.
@daniel-montalvo - do we need all of "row inside treegrid" in backticks or just "row" and "treegrid", in that sentence?
| </tbody> | ||
| </table> | ||
|
|
||
| <h4 id="role-th-scope-column">`TH`</h4> |
There was a problem hiding this comment.
| <h4 id="role-th-scope-column">`TH`</h4> | |
| <h4 id="role-th-scope-column">`TH` <span class="el-context">(`Scope` = `Column` and `Headers` array not set)</span></h4> |
There was a problem hiding this comment.
To me @PaulRayius-2 's suggestion would be the correct use of el-context as per https://github.com/w3c/aria/blob/main/html-aam/index.html
|
Thanks @zakkinsey This should really go in https://github.com/w3c/aria/ We are only using the PDF_AAM repo for collecting issues, but the specifications are being generated from the ARIA monorepo. |
Hi Daniel, yes we understand that pipeline, however we needed a method to better correct our exports prior to integrating them into the main index.html in the ARIA monorepo. So, with that in mind here is the new process we decided upon in our recent PDF Association meeting. We will open a PR for each export here in the PDF-AAM repo with just an HTML snippet. We will use the PR features for suggestions, comments, feedback, etc. We are not able to achieve the same functionality without a PR. Then, once the export snippet is to the place we believe it is ready to be integrated into the index.html we will do that in the main aria monorepo for formal PR review by the ARIA Editors WG. One major benefit of this method is that our HTML snippets are MUCH easier to read and edit vs the large index.html file. Since each of these exports are still requiring a decent amount of additional editing after export from the spreadsheet, especially as we continue to learn W3C's formatting requirements for the AAM, we decided this workflow will enable the fastest and easiest method for asynchronous work as our members working on the project are split between the US and Europe. Will this be an issue? It is not a permanent new pipeline, but rather a bridge to aid in getting us out of the spreadsheet and fully into the index.html. |
| </tbody> | ||
| </table> | ||
|
|
||
| <h4 id="role-th-scope-row">`TH`</h4> |
There was a problem hiding this comment.
| <h4 id="role-th-scope-row">`TH`</h4> | |
| <h4 id="role-th-scope-row">`TH` <span class="el-context">(`Scope` = `Row` and `Headers` array not set)</span></h4> |
| </tbody> | ||
| </table> | ||
|
|
||
| <h4 id="role-th-scope-both">`TH`</h4> |
There was a problem hiding this comment.
| <h4 id="role-th-scope-both">`TH`</h4> | |
| <h4 id="role-th-scope-both">`TH` <span class="el-context">(`Scope` = `Both` and `Headers` array not set)</span></h4> |
| </tbody> | ||
| </table> | ||
|
|
||
| <h4 id="role-th-scope-not-set-headers-array-is-set">`TH`</h4> |
There was a problem hiding this comment.
| <h4 id="role-th-scope-not-set-headers-array-is-set">`TH`</h4> | |
| <h4 id="role-th-scope-not-set-headers-array-is-set">`TH` <span class="el-context">(`Scope` is not set and `Headers` array is not set)</span></h4> |
| </tbody> | ||
| </table> | ||
|
|
||
| <h4 id="role-th-scope-both-headers-array-is-set">`TH`</h4> |
There was a problem hiding this comment.
| <h4 id="role-th-scope-both-headers-array-is-set">`TH`</h4> | |
| <h4 id="role-th-scope-both-headers-array-is-set">`TH` <span class="el-context">(`Scope` = `Both` and `Headers` array is set)</span></h4> |
| </table> | ||
|
|
||
|
|
||
| <h4 id="role-caption-child-of-a-table">`Caption`</h4> |
There was a problem hiding this comment.
| <h4 id="role-caption-child-of-a-table">`Caption`</h4> | |
| <h4 id="role-caption-child-of-a-table">`Caption` <span class="el-context">(child of `Table`)</span></h4> |
Should this say "direct child of table" or is just "child" sufficient?
| </tr> | ||
| <tr> | ||
| <th>Analogous HTML Element</th> | ||
| <td><a class="html-mapping" href="#el-caption">Role: `caption HTML-AAM says to Use WAI-ARIA mapping but there is also other "stuff" there.`</a></td> |
There was a problem hiding this comment.
| <td><a class="html-mapping" href="#el-caption">Role: `caption HTML-AAM says to Use WAI-ARIA mapping but there is also other "stuff" there.`</a></td> | |
| <td><a class="html-mapping" href="#el-caption">Role: `caption` HTML-AAM says to Use WAI-ARIA mapping but there is also other "stuff" there.</a></td> |
Should we remove this: HTML-AAM says to Use WAI-ARIA mapping but there is also other "stuff" there ?
| </tr> | ||
| <tr> | ||
| <th><abbr title="Notes">Notes:</abbr></th> | ||
| <td><span class="property">Note from PDFa: `If a descendant of a table, the first instance of a caption element will provide the table its accessible name.`</span></td> |
There was a problem hiding this comment.
| <td><span class="property">Note from PDFa: `If a descendant of a table, the first instance of a caption element will provide the table its accessible name.`</span></td> | |
| <td><span class="property">Note from PDFa: If a descendant of a `Table`, the first instance of a `Caption` will provide the `Table` its accessible name.</span></td> |
| </tr> | ||
| <tr> | ||
| <th>Analogous HTML Element</th> | ||
| <td><a class="html-mapping" href="Use WAI-ARIA mapping">Role: `Note: There is no analagous HTML element. it is either Header or Column`</a></td> |
There was a problem hiding this comment.
| <td><a class="html-mapping" href="Use WAI-ARIA mapping">Role: `Note: There is no analagous HTML element. it is either Header or Column`</a></td> | |
| <td>Use WAI-ARIA mapping</td> |
| <tbody> | ||
| <tr> | ||
| <th>ARIA Specification</th> | ||
| <td><a class="core-mapping" href="Use WAI-ARIA mapping">Role: `no analagous ARIA role`</a></td> |
There was a problem hiding this comment.
| <td><a class="core-mapping" href="Use WAI-ARIA mapping">Role: `no analagous ARIA role`</a></td> | |
| <td>Use WAI-ARIA mapping</td> |
| <tr><th><abbr title="User Interface Automation">UIA</abbr></th><td>Use WAI-ARIA mapping</td></tr> | ||
| <tr><th><abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology - Service Provider Interface">AT-SPI</abbr></th><td>Use WAI-ARIA mapping</td></tr> | ||
| <tr><th><abbr title="macOS Accessibility Protocol">AX API</abbr></th><td>Use WAI-ARIA mapping</td></tr> | ||
| <tr><th><abbr title="Notes">Notes:</abbr></th><td><span class="property">Note from PDFa: `HTML uses headers array/ IDs for TH and TD https://www.w3.org/TR/html-aam-1.0/#el-th`</span></td></tr> |
There was a problem hiding this comment.
| <tr><th><abbr title="Notes">Notes:</abbr></th><td><span class="property">Note from PDFa: `HTML uses headers array/ IDs for TH and TD https://www.w3.org/TR/html-aam-1.0/#el-th`</span></td></tr> | |
| <tr><th><abbr title="Notes">Notes:</abbr></th><td><span class="property">Note from PDFa: HTML uses `Headers` array / IDs for `TH` and `TD`</span></td></tr> |
| </tr> | ||
| <tr> | ||
| <th>Analogous HTML Element</th> | ||
| <td><a class="html-mapping" href="#el-th">Role: `th Use WAI-ARIA mapping but there are comments`</a></td> |
There was a problem hiding this comment.
| <td><a class="html-mapping" href="#el-th">Role: `th Use WAI-ARIA mapping but there are comments`</a></td> | |
| <td><a class="html-mapping" href="#el-th">Role: `th` Use WAI-ARIA mapping but there are comments</a></td> |
We need to look at those comments and take them into consideration.
| </tr> | ||
| <tr> | ||
| <th>Analogous HTML Element</th> | ||
| <td><a class="html-mapping" href="Use WAI-ARIA mapping">Role: `Note: There is no analagous HTML element. it is either Header or Column`</a></td> |
There was a problem hiding this comment.
| <td><a class="html-mapping" href="Use WAI-ARIA mapping">Role: `Note: There is no analagous HTML element. it is either Header or Column`</a></td> | |
| <td>Use WAI-ARIA mapping</td> |
| <tbody> | ||
| <tr> | ||
| <th>ARIA Specification</th> | ||
| <td><a class="core-mapping" href="Use WAI-ARIA mapping">Role: `no analagous ARIA role`</a></td> |
There was a problem hiding this comment.
| <td><a class="core-mapping" href="Use WAI-ARIA mapping">Role: `no analagous ARIA role`</a></td> | |
| <td>Use WAI-ARIA mapping</td> |
But... how do we use ARIA mapping if there's no analogous ARIA role?
| </tr> | ||
| <tr> | ||
| <th>Analogous HTML Element</th> | ||
| <td><a class="html-mapping" href="#el-th-rowheader">Role: `th (is a row header or row group header)`</a></td> |
There was a problem hiding this comment.
| <td><a class="html-mapping" href="#el-th-rowheader">Role: `th (is a row header or row group header)`</a></td> | |
| <td><a class="html-mapping" href="#el-th-rowheader">Role: `th` (is a row header or row group header)</a></td> |
Do we need to put "el-context" here?
Co-authored-by: Daniel Montalvo <49305434+daniel-montalvo@users.noreply.github.com>
4 participants
Open PR for review features.