Need role for column break

[aleventhal]

Similarly to doc-pagebreak, we need markup to indicate a column break.

Suggest either doc-colbreak or doc-columnbreak.

[TzviyaSiegman]

Would you please clarify how this might be useful in an ARIA setting? Is the intent for AT to announce a column break? As a user, I might find that disruptive. Page breaking and numbering is used to navigate, and it usually not announced at the point of the pagebreak.

If column breaking is for typesetting purposes, then perhaps this is a comment for CSS Multi-Column?

[aleventhal]

Hi, it's for authoring in Google Docs. I agree that out would probably be about when reading, but perhaps useful for authoring. Aaron

…

On Tue, May 15, 2018, 5:28 AM Tzviya ***@***.***> wrote: Would you please clarify how this might be useful in an ARIA setting? Is the intent for AT to announce a column break? As a user, I might find that disruptive. Page breaking and numbering is used to navigate, and it usually not announced at the point of the pagebreak. If column breaking is for typesetting purposes, then perhaps this is a comment for CSS Multi-Column <https://www.w3.org/TR/css-multicol-1/>? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#25 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABUAZk8lykAAjnAEwEiw1Ii8xWUefH_fks5typ_LgaJpZM4T-THz> .

[mattgarrish]

So is the intent to let authors know where their content is being broken when they use a static multi-column layout?

It seems like an interesting feature, if so, but we really haven't tried to branch out into content authoring features. I'm just wondering if this is a feature that needs more discussion within the specific context of web authoring?

One rule we tried to adhere to with the first release of the module was to avoid cherry picking semantics from across publishing domains, and that's the primary concern I would have here. (Even with that approach, we've still faced a lot of questions about why certain semantics are in the module and others are not.)

I don't have the background in authoring tools to say what else might be useful or needed, but my feeling is that perhaps this is something that should be taken up with the ARIA group. There might be a case for a separate authoring semantics module if there are other useful additions.

[aleventhal]

Ok, perhaps we will use
role="separator" aria-roledescription="Column break"

But the advice that this might be annoying to hear is definitely a useful thought.

Feel free to close if you think this is definitely outside the scope of DPUB.

[aleventhal]

Moved to dpub-aria