You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Glk styles have inherent semantics, but that is completely lost in WebGlkOte, and any visual representation of those styles is not accessible somewhat cumbersome to those using screen readers. But it might be possible to wrap the current output of <span>s with HTML elements that express the meaning of the Glk styles. We would have to carefully ensure that any default CSS properties for these elements are reset, as well as making them all inline. So for example, here is how the subheader style, used for a room description, could be output:
Current interpreters like ZVM misuse some of these Glk styles for purely visual formatting. But we could add a Glk extension to allow for broader CSS properties to be set so that ZVM can just say "make this text bold and italic", and then the Glk styles of "headers" and "blockquotes" etc wouldn't be used in weird situations.
Possible ways of expressing the Glk semantics:
Glk style
HTML
Normal
none
Emphasized
<em>
Preformatted
<pre>?
Header
<h2>
Subheader
<h3>
Alert
role="alert"
Note
?
Blockquote
<blockquote>
Input
<kbd>?
User1
none
User2
none
The text was updated successfully, but these errors were encountered:
The Glk styles have inherent semantics, but that is completely lost in WebGlkOte, and any visual representation of those styles is
not accessiblesomewhat cumbersome to those using screen readers. But it might be possible to wrap the current output of<span>
s with HTML elements that express the meaning of the Glk styles. We would have to carefully ensure that any default CSS properties for these elements are reset, as well as making them all inline. So for example, here is how the subheader style, used for a room description, could be output:Current interpreters like ZVM misuse some of these Glk styles for purely visual formatting. But we could add a Glk extension to allow for broader CSS properties to be set so that ZVM can just say "make this text bold and italic", and then the Glk styles of "headers" and "blockquotes" etc wouldn't be used in weird situations.
Possible ways of expressing the Glk semantics:
<em>
<pre>
?<h2>
<h3>
role="alert"
<blockquote>
<kbd>
?The text was updated successfully, but these errors were encountered: