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
Go to a page and enter some text. Make parts bold and other parts italic.
Click to view the HTML of that editable region.
Results
Bold tags use <b> and italic tags use <i>.
Expected results
Bold tags should use <strong> and italic tags should use <em> as these are more semantic.
This came from the Office of Accessibility Services folks who liaison with people who use screen readers. Apparently, screen reader users don't get notified when using <b> and <i>; however, they do get notified with <strong> and <em>.
CleanSlate (read: Mercury Editor) should use <strong> and <em> by default.
Nathan made a change to CleanSlate so that CleanSlate outputs <strong> and <em> tags instead of <b> and <i>. (couldn't find the relevant commit, someone help a brother out).
However, we just received a report from a user that says Chrome on Windows outputs <b> instead of <strong> when using the hotkey.
Steps to reproduce the issue
Use Windows. Log in to CleanSlate using Chrome.
Go to a page and enter some text. Make parts bold using hotkeys (CTRL + B).
Many users are copying and pasting from WORD and this results in <b> and <i> tags on the site. Is it possible to automagically convert <b> and <i> to <strong> and <em> when they hit publish?
Steps to reproduce the issue
Results
Bold tags use
<b>
and italic tags use<i>
.Expected results
Bold tags should use
<strong>
and italic tags should use<em>
as these are more semantic.This came from the Office of Accessibility Services folks who liaison with people who use screen readers. Apparently, screen reader users don't get notified when using
<b>
and<i>
; however, they do get notified with<strong>
and<em>
.CleanSlate (read: Mercury Editor) should use
<strong>
and<em>
by default.Related to #2 and https://stackoverflow.com/questions/271743/whats-the-difference-between-b-and-strong-i-and-em
The text was updated successfully, but these errors were encountered: