Add ASPNET Accessibility Compat Document #484
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@HongGit, |
rpetrusha
suggested changes
Sep 20, 2017
|
|
||
|
|
||
| ### Change Description | ||
| ASP.NET is improving how ASP.NET Web Controls work with accessibility technology in Visual Studio to better support ASP.NET customers. These includ the following changes: |
|
|
||
| ### Change Description | ||
| ASP.NET is improving how ASP.NET Web Controls work with accessibility technology in Visual Studio to better support ASP.NET customers. These includ the following changes: | ||
| - Changes to implement missing UI accessbility patters in controls, like the Add Field dialog in Details View wizard. |
There was a problem hiding this comment.
patters --> patterns
in Details View --> in the Details View
| ### Change Description | ||
| ASP.NET is improving how ASP.NET Web Controls work with accessibility technology in Visual Studio to better support ASP.NET customers. These includ the following changes: | ||
| - Changes to implement missing UI accessbility patters in controls, like the Add Field dialog in Details View wizard. | ||
| - Changes to improve display in High Contrast mode, like the Data Pager Fields Editor. |
| ASP.NET is improving how ASP.NET Web Controls work with accessibility technology in Visual Studio to better support ASP.NET customers. These includ the following changes: | ||
| - Changes to implement missing UI accessbility patters in controls, like the Add Field dialog in Details View wizard. | ||
| - Changes to improve display in High Contrast mode, like the Data Pager Fields Editor. | ||
| - Improve the keyboard navigation experiences for controls, like Configure Object Context Window or Configure Data Source Window, etc. |
There was a problem hiding this comment.
Improve --> Changes to improve
like Configure --> like the Configure
or Configure --> or the Configure
Window, etc. --> Window.
| ### Recommended Action | ||
| +__How to opt in or out of these changes__ | ||
|
|
||
| +In order for the Visual Studio IDE designer to benefit from these changes, it must run on the .NET Framework 4.7.1 or later. The web application can benefit from these changes in either of the following ways: |
There was a problem hiding this comment.
Visual Studio IDE designer, or Visual Studio Designer?
| +__How to opt in or out of these changes__ | ||
|
|
||
| +In order for the Visual Studio IDE designer to benefit from these changes, it must run on the .NET Framework 4.7.1 or later. The web application can benefit from these changes in either of the following ways: | ||
| - Install Visual Studio 2017 15.3 or later, which ships with the following AppContext Switch by default. |
There was a problem hiding this comment.
ships with... --> supports the new accessibility features by default. (Is this correct?)
Question: does the ASP.NET app need to target the .NET Framework 4.7.1.
|
|
||
| +In order for the Visual Studio IDE designer to benefit from these changes, it must run on the .NET Framework 4.7.1 or later. The web application can benefit from these changes in either of the following ways: | ||
| - Install Visual Studio 2017 15.3 or later, which ships with the following AppContext Switch by default. | ||
| - Opt out of the legacy accessibility behaviors by adding the __Switch.UseLegacyAccessibility__ AppContext Switch to the ```<runtime>``` section in the devenv.exe.config file and setting it to false, as the following example shows. |
| - Changes to implement missing UI accessbility patters in controls, like the Add Field dialog in Details View wizard. | ||
| - Changes to improve display in High Contrast mode, like the Data Pager Fields Editor. | ||
| - Improve the keyboard navigation experiences for controls, like Configure Object Context Window or Configure Data Source Window, etc. | ||
|
|
There was a problem hiding this comment.
I think that this needs the following added:
- Quirked
- Build-time break
| </runtime> | ||
| </configuration> | ||
| ``` | ||
| Applications that target the .NET Framework 4.7.1 or later and want to preserve the legacy accessibility behavior can opt in to the use of legacy accessibility features by explicitly setting this AppContext switch to true. |
|
It also occurs to me, @HongGit, that the detail on what accessibility changes were implemented is somewhat sparse. Can you add more detail? |
Contributor
Author
|
@rpetrusha I incorporated your feedback, please review the changes! Could you please clarify a bit more on "more details"? |
rpetrusha
suggested changes
Sep 21, 2017
|
|
||
| ### Change Description | ||
| ASP.NET is improving how ASP.NET Web Controls work with accessibility technology in Visual Studio to better support ASP.NET customers. These include the following changes: | ||
| - Changes to implement missing UI accessbility patterns in controls, like the Add Field dialog in the Details View wizard. |
Contributor
Author
There was a problem hiding this comment.
Will be fixed in the next commit.
svick
reviewed
Sep 21, 2017
|
|
||
| Quirked | ||
|
|
||
| Build-time breake## ASP.NET Accessibility Improvement in .NET 4.7.1 |
Contributor
There was a problem hiding this comment.
The "Quirked" and "Build-time breake" seem to be out of place here.
Contributor
Author
There was a problem hiding this comment.
Will be fixed in the next commit.
| ### Recommended Action | ||
| +__How to opt in or out of these changes__ | ||
|
|
||
| +In order for the Visual Studio Designer to benefit from these changes, it must run on the .NET Framework 4.7.1 or later. The web application can benefit from these changes in either of the following ways: |
Contributor
There was a problem hiding this comment.
The two lines above shouldn't start with a +.
Contributor
Author
There was a problem hiding this comment.
Will be fixed in the next commit.
rpetrusha
pushed a commit
that referenced
this pull request
Oct 17, 2017
* Add headers to dotnet-consumer-projects.md * Tanya's content and Ron's feedback * Next round of changes Second round of feedback plus a couple of bugs. * Fixed version reverted * More bugs * PropertyGrid changes Additional changes for the Property Grid plus some additional tweaks. * Added UIAutomation blurb Added blurb for Nikola's bug and overall UIAutomation improvements. * Incorporating feedback * Bullets Remove extra bullet * feedback * Updates for .net framework 4.7.1 early access build 2539 (#479) * Tanya's Review Tanya's Review * Add ASPNET Accessibility Compat Document (#484) * Add ASPNET Accessibility Compat Document * Update ASPNET Accessibility Improvement.md * Update ASPNET Accessibility Improvement.md @rpetrusha incorporated feedback * ASPNET Accessibility Improvement.md * minor fixups * Update xrefs Found some missing punctuation and updated the xref:s to displayProperty=nameWithType * Add the open source project named surging (#490) * Add the open source project named surging * Correct the problem changes to Libraries * Update dotnet-developer-projects.md * WCF 4.7.1 fixes with appcontext switch document * Fix typo in compatibility README.md (#497) * Create SerialPort-background-thread-exceptions.md (#485) * Create SerialPort-background-thread-exceptions.md * Update SerialPort-background-thread-exceptions.md * Update SerialPort-background-thread-exceptions.md * Update SerialPort-background-thread-exceptions.md * Update SerialPort-background-thread-exceptions.md * Reviewed WCF app compat topics (#496) * Add breaking change docs (#487) * Add breaking change docs * Update Change-SignedXML-and-SignedCMS-default-algorithms-to-SHA256.md * Update Change-SignedXML-and-SignedCMS-default-algorithms-to-SHA256.md * Update RSACng-and-DSACng-not-usable-in-Partial-Trust-scenarios.md * Update SignedXml.GetPublicKey-returns-RSACng-on-net462.md * Update docs for SignedXML fixes * Remove unclosed comment in doc * Fixup some SignedXml docs * Fixup some SignedXml docs * Added AspectCore to .NET Open Source Developer Projects (#495) AspectCore is an Aspect-Oriented Programming based cross platform framework for .NET Core and .NET Framework. Core support for aspect-interceptor,dependency injection integration , web applications , and more. * .NET Native 2.0 initial draft * Fixes based on feedback and rename the file. (#501) * Add ASPNET Accessibility Compat Document * Update ASPNET Accessibility Improvement.md * Update ASPNET Accessibility Improvement.md @rpetrusha incorporated feedback * ASPNET Accessibility Improvement.md * minor fixups * Add more details and rename the file * Update README.md formatting * Update README.md formatting * Update README.md formatting * Correct name of Visual Studio 2017 Version 15.4 * Update funceval.md * FuncEval release notes Add VS screen shots for funceval notes * fix typo * Update incremental-compilation.md * Update links of Win Application Framework (WAF) and Waf DotNetPad (#503) * Update wording * Update link of Waf Music Manager (#502) * Update link of Waf Music Manager * makes fun --> makes it fun * Fixing version number * Fix broken docId * Fixing DocIds * Fixed 3 broken links * Added 2 4.5 changes, fixed formatting (#508) * Corrections to WinForms accessibility topic (#511) * Removed leftover plural (#515) * Changes to parallel changes to dotnet/docs repo (#512) * Added 4.7 JIT issue (#516) * Added JIT issue * Added JIT issue * Added readme.md * Added link to GitHub issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add ASP.NET .NET 4.7.1 Accessibility Compat Documentation.