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
When using UnicodeMath (linear mode) in Word 365's Equation Editor, there are unexpected consequences of altering the Math AutoCorrect settings. The consequences manifest as inappropriate inconsistencies in how expressions are converted to professional format between Display Math and Inline Math.
Depending on the settings (detailed below) the conversion process of Inline Math expressions may inappropriately retain the spaces used to terminate Math AutoCorrect keywords or even fail to convert into professional form at all. If the same expressions are entered as Display Math equations then the spacing is as expected and conversions are successful.
These issues are particularly problematic for screen reader users who need specific AutoCorrect settings for accessibility and may not notice that expressions fail to convert to professional form when explicitly requested.
Tested Version Information
OS Version:
-- OS Name: Microsoft Windows 11 Enterprise
-- Version: 10.0.22621 Build 22621
-- Locale: United States
Microsoft Word Version:
-- Microsoft 365 Apps for enterprise
-- Version 2402 (Build 17328.20612 Click-to-Run) Semi-Annual Enterprise Channel
Environment
Application: Microsoft Word 365
Feature: Equation Editor
Input Method: UnicodeMath (linear mode)
Relevant Settings (note specific changes to these settings as mentioned in the discussion):
Equation Options dialog
"Automatically convert expressions to professional format"
"Math AutoCorrect" tab on the "AutoCorrect" options dialog
"Use Math AutoCorrect rules outside of math regions"
"Replace text as you type"
Issue 1: Unexpected Retention of Math AutoCorrect Terminator Space(s) in Inline Math Expressions
Expected Behavior
Both Display Math and Inline Math should handle Math AutoCorrect keyword terminating spaces consistently
Example: A\cup B should convert to A∪B in both modes
Configuration
These settings are disabled:
Equation Options dialog
"Automatically convert expressions to professional format" unchecked
Math AutoCorrect tab on AutoCorrect dialog
"Replace text as you type" unchecked
This setting is left enabled:
Math AutoCorrect tab on AutoCorrect dialog
"Use Math AutoCorrect rules outside of math regions" checked
Actual Behavior
Display Math (expression alone on line):
Input: A\cup B
Result: A∪B (correct - terminating space removed)
Inline Math (expression within text):
Input: A\cup B
Result: A∪ B (incorrect - terminating space retained)
Impact
Inconsistent visual presentation
Potentially misleading mathematical spacing
Affects document consistency
Would lead to non-visual writers unintentionally creating "sloppy" work and could lead to them being perceived negatively
Issue 2: Failed Professional Format Conversion with "Use Math AutoCorrect rules outside of math regions" Disabled
Configuration
All following settings disabled:
Equation Options dialog
"Automatically convert expressions to professional format" unchecked
Math AutoCorrect tab on AutoCorrect dialog
"Use Math AutoCorrect rules outside of math regions" unchecked
"Replace text as you type" unchecked
Expected Behavior
Math AutoCorrect symbols should convert to professional format when explicitly requested
Conversion should work successfully in both Display and Inline Math
Actual Behavior
Display Math:
Input: A\cup B
Converts correctly to A∪B when professional format requested
Inline Math:
Input: A\cup B
Remains unchanged as A\cup B even when professional format conversion is requested
Conversion fails regardless of method:
Ribbon command
Equation editor dropdown menu
Ctrl+= shortcut
Accessibility Impact
Screen reader users often need to disable AutoCorrect settings to:
Avoid automatic conversion to built-up structures
Prevent confusion from unexpected placeholders
Maintain better control over expression input
These inconsistencies create additional challenges:
Unpredictable behavior between Display and Inline Math
Inability to convert inline expressions when using certain Math AutoCorrect settings
Non-visual users may not notice an expression failed to convert
Increased cognitive load when writing mathematical content
Steps to Reproduce
Issue 1 (Space Retention):
Ensure default AutoCorrect settings are configured as:
Disabled:
Equation Options dialog
"Automatically convert expressions to professional format" unchecked
Math AutoCorrect tab on AutoCorrect dialog
"Replace text as you type" unchecked
Enabled:
Math AutoCorrect tab on AutoCorrect dialog
"Use Math AutoCorrect rules outside of math regions" checked
Create Display Math equation (Alt+=) on empty line
Enter A\cup B
Convert to professional
Note correct spacing
Create Inline Math equation at the end of some text (on the same line)
Enter A\cup B
Convert to professional
Note incorrect space retention
Issue 2 (Failed Conversion):
Disable all three AutoCorrect settings mentioned above
All following settings disabled:
Equation Options dialog
"Automatically convert expressions to professional format" unchecked
Math AutoCorrect tab on AutoCorrect dialog
"Use Math AutoCorrect rules outside of math regions" unchecked
"Replace text as you type" unchecked
Create Display Math equation (Alt+=) on empty line
Enter A\cup B
Convert to professional
Note successful conversion
Create Inline Math equation at the end of some text (on the same line)
Enter A\cup B
Attempt to convert to professional format using any available method
Note that all attempts fail
Suggested Fix
Standardize space handling between Display and Inline Math
Ensure professional format conversion works independently of AutoCorrect settings
Consider adding screen reader notifications for successful/unsuccessful conversions
The text was updated successfully, but these errors were encountered:
Description
When using UnicodeMath (linear mode) in Word 365's Equation Editor, there are unexpected consequences of altering the Math AutoCorrect settings. The consequences manifest as inappropriate inconsistencies in how expressions are converted to professional format between Display Math and Inline Math.
Depending on the settings (detailed below) the conversion process of Inline Math expressions may inappropriately retain the spaces used to terminate Math AutoCorrect keywords or even fail to convert into professional form at all. If the same expressions are entered as Display Math equations then the spacing is as expected and conversions are successful.
It might be helpful to watch the demo Video: Changes in Math AutoCorrect Settings Cause Inconsistent UnicodeMath to Professional Format Conversion Between Display and Inline Math
These issues are particularly problematic for screen reader users who need specific AutoCorrect settings for accessibility and may not notice that expressions fail to convert to professional form when explicitly requested.
Tested Version Information
OS Version:
-- OS Name: Microsoft Windows 11 Enterprise
-- Version: 10.0.22621 Build 22621
-- Locale: United States
Microsoft Word Version:
-- Microsoft 365 Apps for enterprise
-- Version 2402 (Build 17328.20612 Click-to-Run) Semi-Annual Enterprise Channel
Environment
Issue 1: Unexpected Retention of Math AutoCorrect Terminator Space(s) in Inline Math Expressions
Expected Behavior
A\cup B
should convert toA∪B
in both modesConfiguration
These settings are disabled:
This setting is left enabled:
Actual Behavior
A\cup B
A∪B
(correct - terminating space removed)A\cup B
A∪ B
(incorrect - terminating space retained)Impact
Issue 2: Failed Professional Format Conversion with "Use Math AutoCorrect rules outside of math regions" Disabled
Configuration
All following settings disabled:
Expected Behavior
Actual Behavior
A\cup B
A∪B
when professional format requestedA\cup B
A\cup B
even when professional format conversion is requestedAccessibility Impact
Steps to Reproduce
Issue 1 (Space Retention):
A\cup B
A\cup B
Issue 2 (Failed Conversion):
All following settings disabled:
A\cup B
A\cup B
Suggested Fix
The text was updated successfully, but these errors were encountered: